Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 868681eb8b40091b08c014c9acbbb74706faa7f9f806fa44dd0911a0358a7530

Tx prefix hash: c339b5adf0f397c66e24e241c309cfafa4708627266bda0c563346cc08a8e3d0
Tx public key: 581d6b1365bd394c6a09838cdfd3626bbfe07263d2f31e28e9074ba77a8a4dca
Timestamp: 1719184095 Timestamp [UCT]: 2024-06-23 23:08:15 Age [y:d:h:m:s]: 00:296:11:11:44
Block: 1050784 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 211861 RingCT/type: yes/0
Extra: 01581d6b1365bd394c6a09838cdfd3626bbfe07263d2f31e28e9074ba77a8a4dca02110000000552d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 019a79920494ec764b5f4b0cc195086b0a1d89a177d11e081b5bb8e1b8d8e86f 0.600000000000 1520959 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": 1050794, "vin": [ { "gen": { "height": 1050784 } } ], "vout": [ { "amount": 600000000, "target": { "key": "019a79920494ec764b5f4b0cc195086b0a1d89a177d11e081b5bb8e1b8d8e86f" } } ], "extra": [ 1, 88, 29, 107, 19, 101, 189, 57, 76, 106, 9, 131, 140, 223, 211, 98, 107, 191, 224, 114, 99, 210, 243, 30, 40, 233, 7, 75, 167, 122, 138, 77, 202, 2, 17, 0, 0, 0, 5, 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