Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 89dac21e1b5f3ffc7ab920583dc1dbce66eb56b19087e09b9517ce07596b7fe0

Tx prefix hash: 4d430ea3169986dbcd21041faad1a640453761dfea6ed45505af8a91e93e755e
Tx public key: dd843bdc1cfe9f3f4046e99966b485e176f0274dbe4c5b7a338019478286fe55
Timestamp: 1647931459 Timestamp [UCT]: 2022-03-22 06:44:19 Age [y:d:h:m:s]: 02:327:20:27:22
Block: 463786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 753586 RingCT/type: yes/0
Extra: 01dd843bdc1cfe9f3f4046e99966b485e176f0274dbe4c5b7a338019478286fe55021100000003bf7ee4e7000000000000000000

1 output(s) for total of 17.835476386000 dcy

stealth address amount amount idx
00: b73cf37ebf31f8f89b9f5984e9d8e9e9547c7631d527844b7f52132efef0b3a6 17.835476386000 881527 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": 463796, "vin": [ { "gen": { "height": 463786 } } ], "vout": [ { "amount": 17835476386, "target": { "key": "b73cf37ebf31f8f89b9f5984e9d8e9e9547c7631d527844b7f52132efef0b3a6" } } ], "extra": [ 1, 221, 132, 59, 220, 28, 254, 159, 63, 64, 70, 233, 153, 102, 180, 133, 225, 118, 240, 39, 77, 190, 76, 91, 122, 51, 128, 25, 71, 130, 134, 254, 85, 2, 17, 0, 0, 0, 3, 191, 126, 228, 231, 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