Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 686eab851a09fd3ddb56484a430b7db3c129585e51cd3281cb817bd2bf8df1b5

Tx prefix hash: 0d5e07333c71f54d537e00e7a10227f65ad24130ad3c302e6c050b741e2c01ad
Tx public key: fa2204c7c7a92086e54c2a3f824d20391c66692db5681b16fa51dc64ffafff4a
Timestamp: 1577463127 Timestamp [UCT]: 2019-12-27 16:12:07 Age [y:d:h:m:s]: 04:315:00:12:43
Block: 32941 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1114261 RingCT/type: yes/0
Extra: 01fa2204c7c7a92086e54c2a3f824d20391c66692db5681b16fa51dc64ffafff4a02110000000b8a2ee0d9000000000000000000

1 output(s) for total of 477.572921932000 dcy

stealth address amount amount idx
00: 398f98d17ccf6be6de2a744895ac5a547b37ebf81f3b540cccf61747211b2f5b 477.572921932000 54963 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": 32951, "vin": [ { "gen": { "height": 32941 } } ], "vout": [ { "amount": 477572921932, "target": { "key": "398f98d17ccf6be6de2a744895ac5a547b37ebf81f3b540cccf61747211b2f5b" } } ], "extra": [ 1, 250, 34, 4, 199, 199, 169, 32, 134, 229, 76, 42, 63, 130, 77, 32, 57, 28, 102, 105, 45, 181, 104, 27, 22, 250, 81, 220, 100, 255, 175, 255, 74, 2, 17, 0, 0, 0, 11, 138, 46, 224, 217, 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