Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: afad481727d9d79a73162753aaf1656bc75296a0a21e5087aeb46910836fd38b

Tx prefix hash: c502607397b86d05732df9ecf527ef63d1708e6fdba2e3a72c37daac813119c9
Tx public key: baabb069fd2c84dbe3a5c4cca9300f37c879956b8a32394b5d1d43d5a53263db
Timestamp: 1707380207 Timestamp [UCT]: 2024-02-08 08:16:47 Age [y:d:h:m:s]: 01:087:03:58:27
Block: 952924 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323369 RingCT/type: yes/0
Extra: 01baabb069fd2c84dbe3a5c4cca9300f37c879956b8a32394b5d1d43d5a53263db02110000002159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82bcd3eafb618c6abb4394b410d2cf1034f657259873a2e680b5d76bd48b304c 0.600000000000 1412064 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": 952934, "vin": [ { "gen": { "height": 952924 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82bcd3eafb618c6abb4394b410d2cf1034f657259873a2e680b5d76bd48b304c" } } ], "extra": [ 1, 186, 171, 176, 105, 253, 44, 132, 219, 227, 165, 196, 204, 169, 48, 15, 55, 200, 121, 149, 107, 138, 50, 57, 75, 93, 29, 67, 213, 165, 50, 99, 219, 2, 17, 0, 0, 0, 33, 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