Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7d408ae56318881c30bc6b8bd9a2685c30c4a482a1093913a19204666a18c84

Tx prefix hash: 6868b6a98c0b3fbd6474cf70aa2349cdba1eb5bdcc6e78cab07f3e14a55d655a
Tx public key: a345a708c002c68ca4b7ee771e5ad2aef1b76f05e951ee5bff08c5f9c95d137c
Timestamp: 1709733692 Timestamp [UCT]: 2024-03-06 14:01:32 Age [y:d:h:m:s]: 00:324:08:59:16
Block: 972455 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 232137 RingCT/type: yes/0
Extra: 01a345a708c002c68ca4b7ee771e5ad2aef1b76f05e951ee5bff08c5f9c95d137c02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 85a663c23e7cbec4b23fd633cff921f6096162effe5dd842f85a3ad85bdcf176 0.600000000000 1432368 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": 972465, "vin": [ { "gen": { "height": 972455 } } ], "vout": [ { "amount": 600000000, "target": { "key": "85a663c23e7cbec4b23fd633cff921f6096162effe5dd842f85a3ad85bdcf176" } } ], "extra": [ 1, 163, 69, 167, 8, 192, 2, 198, 140, 164, 183, 238, 119, 30, 90, 210, 174, 241, 183, 111, 5, 233, 81, 238, 91, 255, 8, 197, 249, 201, 93, 19, 124, 2, 17, 0, 0, 0, 7, 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