Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d346fae128f5c211dacd91116d4da75bac224939144e8177550ed292e5ddaf5d

Tx prefix hash: a31dbb4c5cd8bc3c3ad53c45693e88720317fa41ed4222e86a82b0f8a860cae1
Tx public key: d38e952d90797810ee15e4687d67c204853fe9140f64df1586f2cb869c4b13a1
Timestamp: 1749534214 Timestamp [UCT]: 2025-06-10 05:43:34 Age [y:d:h:m:s]: 00:156:18:14:41
Block: 1301859 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 109718 RingCT/type: yes/0
Extra: 01d38e952d90797810ee15e4687d67c204853fe9140f64df1586f2cb869c4b13a1021100000002d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 52c13d1f951c9ef3af74ea2f69bead1e2df1236030a35b5846efcb2545ea2e00 0.600000000000 1789422 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": 1301869, "vin": [ { "gen": { "height": 1301859 } } ], "vout": [ { "amount": 600000000, "target": { "key": "52c13d1f951c9ef3af74ea2f69bead1e2df1236030a35b5846efcb2545ea2e00" } } ], "extra": [ 1, 211, 142, 149, 45, 144, 121, 120, 16, 238, 21, 228, 104, 125, 103, 194, 4, 133, 63, 233, 20, 15, 100, 223, 21, 134, 242, 203, 134, 156, 75, 19, 161, 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