Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4f988d2be33fd889df672b59894ca1d67054ae7f9493b7fcbcbee099245cff6f

Tx prefix hash: dcc62273f072d9f32ff3f4120439f5914c668ce5f4e8fba9fbbf91c5386e5469
Tx public key: 0498e1a04cc666c5a6ec626aae33e256fee2ebff3da28dbde0da4de1e019200e
Timestamp: 1712258483 Timestamp [UCT]: 2024-04-04 19:21:23 Age [y:d:h:m:s]: 01:054:11:29:22
Block: 993360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 299960 RingCT/type: yes/0
Extra: 010498e1a04cc666c5a6ec626aae33e256fee2ebff3da28dbde0da4de1e019200e0211000000030011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 51b121c8a70df8bcf6eb766a596ca4167b86c3c0daf07aed607f1352ea4dd16b 0.600000000000 1453746 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": 993370, "vin": [ { "gen": { "height": 993360 } } ], "vout": [ { "amount": 600000000, "target": { "key": "51b121c8a70df8bcf6eb766a596ca4167b86c3c0daf07aed607f1352ea4dd16b" } } ], "extra": [ 1, 4, 152, 225, 160, 76, 198, 102, 197, 166, 236, 98, 106, 174, 51, 226, 86, 254, 226, 235, 255, 61, 162, 141, 189, 224, 218, 77, 225, 224, 25, 32, 14, 2, 17, 0, 0, 0, 3, 0, 17, 5, 91, 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