Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9c9e94fbdd2fa7a017fe708ddd8ccb11fb69fbc3b9ff57e7f310762d060383c9

Tx prefix hash: 76887186175064b09fefe2ea01a13de1d3d7f5707b87d5c3543ee626a0d9d7bf
Tx public key: 8a7cf0648a1b82e8501a325448b3adb2679c3fb40102059bf261765f18ac905e
Timestamp: 1585550877 Timestamp [UCT]: 2020-03-30 06:47:57 Age [y:d:h:m:s]: 05:194:09:29:56
Block: 89903 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1296370 RingCT/type: yes/0
Extra: 018a7cf0648a1b82e8501a325448b3adb2679c3fb40102059bf261765f18ac905e02110000000b37fb5df4000000000000000000

1 output(s) for total of 309.111253256000 dcy

stealth address amount amount idx
00: dc1c5041cb0085b5c5f8245f004234ebb91b6f0f491f0e52e41dbcfd8e6274a5 309.111253256000 161111 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": 89913, "vin": [ { "gen": { "height": 89903 } } ], "vout": [ { "amount": 309111253256, "target": { "key": "dc1c5041cb0085b5c5f8245f004234ebb91b6f0f491f0e52e41dbcfd8e6274a5" } } ], "extra": [ 1, 138, 124, 240, 100, 138, 27, 130, 232, 80, 26, 50, 84, 72, 179, 173, 178, 103, 156, 63, 180, 1, 2, 5, 155, 242, 97, 118, 95, 24, 172, 144, 94, 2, 17, 0, 0, 0, 11, 55, 251, 93, 244, 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