Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4386f573c84d6f2e38ed5009f0cb2e621d7c138111922e0afdda3fc4c7b6e159

Tx prefix hash: 5349583fb8f774708ff182609a9dc011b755e391021654739642e6d78a77eb04
Tx public key: a2861e38a7180a0f44a3b974d1e00185392f69105b2ffe3c32accb9fd3e1361f
Timestamp: 1716868058 Timestamp [UCT]: 2024-05-28 03:47:38 Age [y:d:h:m:s]: 00:156:20:53:32
Block: 1031593 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112290 RingCT/type: yes/0
Extra: 01a2861e38a7180a0f44a3b974d1e00185392f69105b2ffe3c32accb9fd3e1361f0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 60fb992a092841e907a6656a62ad1065e9caf3f8eb8c4c3cf1da748cd93655fe 0.600000000000 1500042 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": 1031603, "vin": [ { "gen": { "height": 1031593 } } ], "vout": [ { "amount": 600000000, "target": { "key": "60fb992a092841e907a6656a62ad1065e9caf3f8eb8c4c3cf1da748cd93655fe" } } ], "extra": [ 1, 162, 134, 30, 56, 167, 24, 10, 15, 68, 163, 185, 116, 209, 224, 1, 133, 57, 47, 105, 16, 91, 47, 254, 60, 50, 172, 203, 159, 211, 225, 54, 31, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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