Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 719ae218467bf15153e0db15edea0ec70717ebbbac52f1bcbf11fd9d8eca7c24

Tx prefix hash: a43310d08b124d07680af6161503509a82609a3a7357acbaa2a9c7092bc93e8d
Tx public key: 0c09f5548ab93ffdf32a3ea9af21f20e43313c5b2d8c8d352288d7b28af2daf3
Timestamp: 1647931246 Timestamp [UCT]: 2022-03-22 06:40:46 Age [y:d:h:m:s]: 02:280:09:31:21
Block: 463784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 719903 RingCT/type: yes/0
Extra: 010c09f5548ab93ffdf32a3ea9af21f20e43313c5b2d8c8d352288d7b28af2daf302110000000cbf7ee4e7000000000000000000

1 output(s) for total of 17.835748537000 dcy

stealth address amount amount idx
00: f3f47f909c6a2cdcba4ed53334fadd3f638e3c83a1ed3c3c5a1f845dcf259e99 17.835748537000 881525 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": 463794, "vin": [ { "gen": { "height": 463784 } } ], "vout": [ { "amount": 17835748537, "target": { "key": "f3f47f909c6a2cdcba4ed53334fadd3f638e3c83a1ed3c3c5a1f845dcf259e99" } } ], "extra": [ 1, 12, 9, 245, 84, 138, 185, 63, 253, 243, 42, 62, 169, 175, 33, 242, 14, 67, 49, 60, 91, 45, 140, 141, 53, 34, 136, 215, 178, 138, 242, 218, 243, 2, 17, 0, 0, 0, 12, 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