Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 570a08e28f222c5cfbc1ae72e89608b6bb9a3323f2b49322dc057dc7cd6d5d09

Tx prefix hash: 9dc6e49d53557d03adb47994896fcd1e7f6c821db8533ead0ce4ce3d07f538c1
Tx public key: e6c643cfa2ebfaba77bee9c74dd19b77f422f664d21b2f2c3862d26ba7e5e11e
Timestamp: 1731422888 Timestamp [UCT]: 2024-11-12 14:48:08 Age [y:d:h:m:s]: 00:146:20:42:08
Block: 1152167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 104784 RingCT/type: yes/0
Extra: 01e6c643cfa2ebfaba77bee9c74dd19b77f422f664d21b2f2c3862d26ba7e5e11e0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 47d95989859444d860b8398d4a48a6a512086616f178bfe1f90e94497b6c712e 0.600000000000 1637758 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": 1152177, "vin": [ { "gen": { "height": 1152167 } } ], "vout": [ { "amount": 600000000, "target": { "key": "47d95989859444d860b8398d4a48a6a512086616f178bfe1f90e94497b6c712e" } } ], "extra": [ 1, 230, 198, 67, 207, 162, 235, 250, 186, 119, 190, 233, 199, 77, 209, 155, 119, 244, 34, 246, 100, 210, 27, 47, 44, 56, 98, 210, 107, 167, 229, 225, 30, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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