Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 34546958a3168bdeefa7666bd98b08d6890318d61ddc61899d33b34d30b11681

Tx prefix hash: a91fdc796ef5e2a8775f600d1d07657d1504d258c32089db4be10c661377dd9e
Tx public key: 4c7d9ba867dcfbc1df77922a59107914bec1db8ed3cc0cc281cf66e1bdc2369a
Timestamp: 1754617675 Timestamp [UCT]: 2025-08-08 01:47:55 Age [y:d:h:m:s]: 00:111:19:16:41
Block: 1342498 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 79019 RingCT/type: yes/0
Extra: 014c7d9ba867dcfbc1df77922a59107914bec1db8ed3cc0cc281cf66e1bdc2369a02110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b5b9a5aad50b3ff0ea2ea3c000e1c2b457759d3bf704712b73b64a9f8f1440d 0.600000000000 1830329 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": 1342508, "vin": [ { "gen": { "height": 1342498 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b5b9a5aad50b3ff0ea2ea3c000e1c2b457759d3bf704712b73b64a9f8f1440d" } } ], "extra": [ 1, 76, 125, 155, 168, 103, 220, 251, 193, 223, 119, 146, 42, 89, 16, 121, 20, 190, 193, 219, 142, 211, 204, 12, 194, 129, 207, 102, 225, 189, 194, 54, 154, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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