Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3089a72c8538494b824a39fc8ff2eb2c32143aa1a07031f77f5fd7fc8b3cad62

Tx prefix hash: 5b47cbca3ebcb19f62fc756337f110f658fd772c6c07cce5da2aee943736277f
Tx public key: 6790e8a2000c19ff96c1157457fba6d0274de7880dc6c1a90fb24c691ae98a98
Timestamp: 1633637484 Timestamp [UCT]: 2021-10-07 20:11:24 Age [y:d:h:m:s]: 03:049:15:11:29
Block: 348639 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 812727 RingCT/type: yes/0
Extra: 016790e8a2000c19ff96c1157457fba6d0274de7880dc6c1a90fb24c691ae98a980211000000033fc41461000000000000000000

1 output(s) for total of 42.935318707000 dcy

stealth address amount amount idx
00: 6ad771d27da60c3bdd1d0d675e3c6ac12a4bbe162d45b70d00557624000ae187 42.935318707000 713907 of 0

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": 348649, "vin": [ { "gen": { "height": 348639 } } ], "vout": [ { "amount": 42935318707, "target": { "key": "6ad771d27da60c3bdd1d0d675e3c6ac12a4bbe162d45b70d00557624000ae187" } } ], "extra": [ 1, 103, 144, 232, 162, 0, 12, 25, 255, 150, 193, 21, 116, 87, 251, 166, 208, 39, 77, 231, 136, 13, 198, 193, 169, 15, 178, 76, 105, 26, 233, 138, 152, 2, 17, 0, 0, 0, 3, 63, 196, 20, 97, 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