Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ed22d82d9dff3702cc1df9410038f149f1ec0a7b53b1c5c15b652eb6cae9453b

Tx prefix hash: ff7e38c5ba574a15ead514616d7f82e6ac17aa8e521d405f0922109cd643e587
Tx public key: 3aa7830f5dd5d324076511d0f40a6529024ba47127aee9173caddd5bcf0a3a93
Timestamp: 1588265206 Timestamp [UCT]: 2020-04-30 16:46:46 Age [y:d:h:m:s]: 04:210:13:38:36
Block: 97085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1064849 RingCT/type: yes/0
Extra: 013aa7830f5dd5d324076511d0f40a6529024ba47127aee9173caddd5bcf0a3a930211000000046fa03929000000000000000000

1 output(s) for total of 292.629334260000 dcy

stealth address amount amount idx
00: 6205c01d4bf036befd9af3c601240c40505e36e91625e5f93880b5d2f1793082 292.629334260000 172096 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": 97095, "vin": [ { "gen": { "height": 97085 } } ], "vout": [ { "amount": 292629334260, "target": { "key": "6205c01d4bf036befd9af3c601240c40505e36e91625e5f93880b5d2f1793082" } } ], "extra": [ 1, 58, 167, 131, 15, 93, 213, 211, 36, 7, 101, 17, 208, 244, 10, 101, 41, 2, 75, 164, 113, 39, 174, 233, 23, 60, 173, 221, 91, 207, 10, 58, 147, 2, 17, 0, 0, 0, 4, 111, 160, 57, 41, 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