Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 786872fa81949755e64e8cefafe218e4450976d51fd97df0bbc3cf238238d1ba

Tx prefix hash: 431c753f203109af91457fdf5cbab678016b3dbc40f4577a0a2c165eaab1b52b
Tx public key: e34cb7b1f53c0b4597a4b2083d50f03cfb37340ea83a9e22e9da2ec9974230c4
Timestamp: 1704678882 Timestamp [UCT]: 2024-01-08 01:54:42 Age [y:d:h:m:s]: 01:093:01:51:42
Block: 930514 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 327646 RingCT/type: yes/0
Extra: 01e34cb7b1f53c0b4597a4b2083d50f03cfb37340ea83a9e22e9da2ec9974230c402110000000652d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: cc88d6d44acd5dc0472a70ba47bff757ea77bbd6ad61750aad787659e877c4cf 0.600000000000 1388396 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": 930524, "vin": [ { "gen": { "height": 930514 } } ], "vout": [ { "amount": 600000000, "target": { "key": "cc88d6d44acd5dc0472a70ba47bff757ea77bbd6ad61750aad787659e877c4cf" } } ], "extra": [ 1, 227, 76, 183, 177, 245, 60, 11, 69, 151, 164, 178, 8, 61, 80, 240, 60, 251, 55, 52, 14, 168, 58, 158, 34, 233, 218, 46, 201, 151, 66, 48, 196, 2, 17, 0, 0, 0, 6, 82, 212, 126, 148, 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