Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3d6b5205809e943f8cbc799a8904efe1b58dad118457812364cf6dbdf56bd3c6

Tx prefix hash: e9b548cfe09df6bd782ec0485883500b2abe5e05f32174c9ee5cf00a817c35fd
Tx public key: 354aa0be10f52d366f39eae69c73b3e837b0c380a8b32fa9a998417b78b44718
Timestamp: 1751824275 Timestamp [UCT]: 2025-07-06 17:51:15 Age [y:d:h:m:s]: 00:137:23:59:21
Block: 1320070 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 97035 RingCT/type: yes/0
Extra: 01354aa0be10f52d366f39eae69c73b3e837b0c380a8b32fa9a998417b78b44718021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a53ab96dca91fae30288c27ffc49438e9a92958960cd8f0840006783ce77c2a5 0.600000000000 1807765 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": 1320080, "vin": [ { "gen": { "height": 1320070 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a53ab96dca91fae30288c27ffc49438e9a92958960cd8f0840006783ce77c2a5" } } ], "extra": [ 1, 53, 74, 160, 190, 16, 245, 45, 54, 111, 57, 234, 230, 156, 115, 179, 232, 55, 176, 195, 128, 168, 179, 47, 169, 169, 152, 65, 123, 120, 180, 71, 24, 2, 17, 0, 0, 0, 2, 216, 231, 210, 65, 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