Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 80d68f850420a578a53f7cf8c6c809fc6eb6c2b6dc38ca9f6e4b31ec4abfbbe1

Tx prefix hash: 581428fdfc3f24d034a77b9ce5893cb1b7ed4dc598b405dbc8e4357c88c6237f
Tx public key: aa154c90a217adcae960a7586896a24e4f40d80e4bd54c31e9483dbe4c75902c
Timestamp: 1727170935 Timestamp [UCT]: 2024-09-24 09:42:15 Age [y:d:h:m:s]: 00:121:11:28:17
Block: 1117007 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 86814 RingCT/type: yes/0
Extra: 01aa154c90a217adcae960a7586896a24e4f40d80e4bd54c31e9483dbe4c75902c02110000000791e13c04000000000000000000

1 output(s) for total of 0.608000000000 dcy

stealth address amount amount idx
00: 5a2d4fd55f509aff10e865c39306f229251ad0a329fe859692f40bd3d5ae8c89 0.608000000000 1597686 of 0

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": 1117017, "vin": [ { "gen": { "height": 1117007 } } ], "vout": [ { "amount": 608000000, "target": { "key": "5a2d4fd55f509aff10e865c39306f229251ad0a329fe859692f40bd3d5ae8c89" } } ], "extra": [ 1, 170, 21, 76, 144, 162, 23, 173, 202, 233, 96, 167, 88, 104, 150, 162, 78, 79, 64, 216, 14, 75, 213, 76, 49, 233, 72, 61, 190, 76, 117, 144, 44, 2, 17, 0, 0, 0, 7, 145, 225, 60, 4, 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