Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4e12d25443c5e926af4aa96d3e1e4054d7c3f94a8bad787e78786e7597a9b067

Tx prefix hash: c403b70178b7169288a152f5924226b001328961946c25609539fd8cbacc9ebd
Tx public key: 852e19588a1f822689cd451ef9389d1c71a5f9ff84af8c6d19d53174d3c6a9bd
Timestamp: 1761871207 Timestamp [UCT]: 2025-10-31 00:40:07 Age [y:d:h:m:s]: 00:068:06:27:05
Block: 1401578 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 48867 RingCT/type: yes/0
Extra: 01852e19588a1f822689cd451ef9389d1c71a5f9ff84af8c6d19d53174d3c6a9bd021100000004df5a247a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d3f81fc71ea0490694ea475e379538501a12605e5a0f970d201b861ac00fce10 0.600000000000 1889897 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": 1401588, "vin": [ { "gen": { "height": 1401578 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d3f81fc71ea0490694ea475e379538501a12605e5a0f970d201b861ac00fce10" } } ], "extra": [ 1, 133, 46, 25, 88, 138, 31, 130, 38, 137, 205, 69, 30, 249, 56, 157, 28, 113, 165, 249, 255, 132, 175, 140, 109, 25, 213, 49, 116, 211, 198, 169, 189, 2, 17, 0, 0, 0, 4, 223, 90, 36, 122, 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