Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22f72cf55acd9179495c8bec5037a73a9402773b0ec220ac250822eec0f674f4

Tx prefix hash: ba50f3c35cc23ad4ef0b6bb3ea77e1a0e426fa95f61591996669bfb86f944c7a
Tx public key: 01bcdc5d16acefa36882ad7fe5414b11a80fb671f6fabcb16f0b44b7f8b1abf6
Timestamp: 1649676022 Timestamp [UCT]: 2022-04-11 11:20:22 Age [y:d:h:m:s]: 02:274:01:47:23
Block: 477937 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 715681 RingCT/type: yes/0
Extra: 0101bcdc5d16acefa36882ad7fe5414b11a80fb671f6fabcb16f0b44b7f8b1abf6021100000013d3fcec30000000000000000000

1 output(s) for total of 16.010192575000 dcy

stealth address amount amount idx
00: ebafbfda8df7fb4a97e3a4b1ea94e58a99ac3f986d98c3ec4641d9b2c335ed9c 16.010192575000 898650 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": 477947, "vin": [ { "gen": { "height": 477937 } } ], "vout": [ { "amount": 16010192575, "target": { "key": "ebafbfda8df7fb4a97e3a4b1ea94e58a99ac3f986d98c3ec4641d9b2c335ed9c" } } ], "extra": [ 1, 1, 188, 220, 93, 22, 172, 239, 163, 104, 130, 173, 127, 229, 65, 75, 17, 168, 15, 182, 113, 246, 250, 188, 177, 111, 11, 68, 183, 248, 177, 171, 246, 2, 17, 0, 0, 0, 19, 211, 252, 236, 48, 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