Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 681dbf0872ba6c04cfa9fa08473bb9b71c7854cb94855ae9c8240a540ca2531e

Tx prefix hash: e0d2fd82148e78d52a19ea9eb2c921462cd465d67909becf714f0c03fbe5ca16
Tx public key: 9a11add8c34c7ae954abedcc5ae06cca98894689dae44af0dbf66a838a8b6af7
Timestamp: 1726597051 Timestamp [UCT]: 2024-09-17 18:17:31 Age [y:d:h:m:s]: 00:116:16:39:00
Block: 1112242 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 83454 RingCT/type: yes/0
Extra: 019a11add8c34c7ae954abedcc5ae06cca98894689dae44af0dbf66a838a8b6af702110000000791e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b044ed5ae840318689679d9269e2e38cfe49739687200d1ee852f0f4dcb2a9d2 0.600000000000 1591497 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": 1112252, "vin": [ { "gen": { "height": 1112242 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b044ed5ae840318689679d9269e2e38cfe49739687200d1ee852f0f4dcb2a9d2" } } ], "extra": [ 1, 154, 17, 173, 216, 195, 76, 122, 233, 84, 171, 237, 204, 90, 224, 108, 202, 152, 137, 70, 137, 218, 228, 74, 240, 219, 246, 106, 131, 138, 139, 106, 247, 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