Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 18da95e3a81170435b7ff8939a38c8c3cab5dac713f56a3c0816c1be845e685d

Tx prefix hash: ba295fcebb2b15652ddbaa86943c8d66db4eaa1b1d8778e6bfd760d8e6b698d3
Tx public key: 6da8d856915a3318021cf567bcb5ea4fab3534b4e8ed42570a1f65c6a839d141
Timestamp: 1712976095 Timestamp [UCT]: 2024-04-13 02:41:35 Age [y:d:h:m:s]: 00:318:03:10:17
Block: 999299 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 227434 RingCT/type: yes/0
Extra: 016da8d856915a3318021cf567bcb5ea4fab3534b4e8ed42570a1f65c6a839d14102110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 96cf189661640e408c8ca3b642d60d3f6febebf454326efa1d3990249e40e20a 0.600000000000 1459777 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 999309, "vin": [ { "gen": { "height": 999299 } } ], "vout": [ { "amount": 600000000, "target": { "key": "96cf189661640e408c8ca3b642d60d3f6febebf454326efa1d3990249e40e20a" } } ], "extra": [ 1, 109, 168, 216, 86, 145, 90, 51, 24, 2, 28, 245, 103, 188, 181, 234, 79, 171, 53, 52, 180, 232, 237, 66, 87, 10, 31, 101, 198, 168, 57, 209, 65, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8