Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1c211e054ad06ed49edb568b6a12d85a843e220b35a4f7de76e9b05ae1f4a7a9

Tx prefix hash: 61068e0e843a3bbf35e0978ba64ce919f59eb366138eca7ed42ec0a048a07de0
Tx public key: c19a6bb83aa7fda4195d53907be525657d13debfca7587ed8d54ca3340d54baf
Timestamp: 1749655870 Timestamp [UCT]: 2025-06-11 15:31:10 Age [y:d:h:m:s]: 00:155:03:55:34
Block: 1302855 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 108573 RingCT/type: yes/0
Extra: 01c19a6bb83aa7fda4195d53907be525657d13debfca7587ed8d54ca3340d54baf021100000003dfc3ba49000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d929868097e0b404d5a2bff8d1abde0b296bf58b82b2fb66ef5847ffecb1f13b 0.600000000000 1790428 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": 1302865, "vin": [ { "gen": { "height": 1302855 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d929868097e0b404d5a2bff8d1abde0b296bf58b82b2fb66ef5847ffecb1f13b" } } ], "extra": [ 1, 193, 154, 107, 184, 58, 167, 253, 164, 25, 93, 83, 144, 123, 229, 37, 101, 125, 19, 222, 191, 202, 117, 135, 237, 141, 84, 202, 51, 64, 213, 75, 175, 2, 17, 0, 0, 0, 3, 223, 195, 186, 73, 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