Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 760e178e84a2599e5ae57a3826f5b48bb38d9f69255c2ee9af145e20c8d5bbae

Tx prefix hash: 9bccd43a363616f64e6cb904e1ccf2b44c1b95cc6248c2ca7429b8e8de699a27
Tx public key: 2f3f9eb3b22ad2c1e495dbf75016ffe89fd90550d9cb109fea1910840a8da091
Timestamp: 1704569465 Timestamp [UCT]: 2024-01-06 19:31:05 Age [y:d:h:m:s]: 01:164:16:04:56
Block: 929613 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 378702 RingCT/type: yes/0
Extra: 012f3f9eb3b22ad2c1e495dbf75016ffe89fd90550d9cb109fea1910840a8da09102110000000852d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 29c7b43d0bd0992e07f860b244812309d816c6a68029aabcdc7ee968420089b9 0.600000000000 1387489 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": 929623, "vin": [ { "gen": { "height": 929613 } } ], "vout": [ { "amount": 600000000, "target": { "key": "29c7b43d0bd0992e07f860b244812309d816c6a68029aabcdc7ee968420089b9" } } ], "extra": [ 1, 47, 63, 158, 179, 178, 42, 210, 193, 228, 149, 219, 247, 80, 22, 255, 232, 159, 217, 5, 80, 217, 203, 16, 159, 234, 25, 16, 132, 10, 141, 160, 145, 2, 17, 0, 0, 0, 8, 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