Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b99847fb27cada4737b19fdb9995db8995ad943a4c263ef8eed61cf368a061e4

Tx prefix hash: d70e9e470768a3c5a7cb7d941f7b57e1893ee6c34614add9770f06d54132f3ae
Tx public key: 52261d26b1da45ae683405a79415783e0aad1ff835830b077e5391df2b75158a
Timestamp: 1703568307 Timestamp [UCT]: 2023-12-26 05:25:07 Age [y:d:h:m:s]: 01:113:02:14:17
Block: 921328 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 341943 RingCT/type: yes/0
Extra: 0152261d26b1da45ae683405a79415783e0aad1ff835830b077e5391df2b75158a0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f559636aeab4d1e5dc906f11519176974c198e93c20124a5da71cae8ea9fcb22 0.600000000000 1379014 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": 921338, "vin": [ { "gen": { "height": 921328 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f559636aeab4d1e5dc906f11519176974c198e93c20124a5da71cae8ea9fcb22" } } ], "extra": [ 1, 82, 38, 29, 38, 177, 218, 69, 174, 104, 52, 5, 167, 148, 21, 120, 62, 10, 173, 31, 248, 53, 131, 11, 7, 126, 83, 145, 223, 43, 117, 21, 138, 2, 17, 0, 0, 0, 2, 122, 156, 244, 199, 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