Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e9ed3a6595b2d7965833e31c913b643c933f71be457cd073268b16984d0aaeb9

Tx prefix hash: cc8ea6eac407f4274e590d6d8911140f385b87d32e198b18f23245de4e3c5906
Tx public key: 8828525c93f7ebf33e8d17b8c4e984069ea4355b929112dc0677922720ba3e31
Timestamp: 1715135194 Timestamp [UCT]: 2024-05-08 02:26:34 Age [y:d:h:m:s]: 00:337:01:55:05
Block: 1017225 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 240951 RingCT/type: yes/0
Extra: 018828525c93f7ebf33e8d17b8c4e984069ea4355b929112dc0677922720ba3e3102110000000b0011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: aac57518870d422fa2ca7c3f7f7486cd588e4faa498579fd6fba7c6da6827c03 0.600000000000 1480994 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": 1017235, "vin": [ { "gen": { "height": 1017225 } } ], "vout": [ { "amount": 600000000, "target": { "key": "aac57518870d422fa2ca7c3f7f7486cd588e4faa498579fd6fba7c6da6827c03" } } ], "extra": [ 1, 136, 40, 82, 92, 147, 247, 235, 243, 62, 141, 23, 184, 196, 233, 132, 6, 158, 164, 53, 91, 146, 145, 18, 220, 6, 119, 146, 39, 32, 186, 62, 49, 2, 17, 0, 0, 0, 11, 0, 17, 5, 91, 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