Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0827c17b8336b1bc66a1a3d683a73e4e11701c4a108c508f3598647b8219ba35

Tx prefix hash: 5ce3138a7f255fa9e419a1e2385d5bf55da9cb9da4df57aed6f38378c42c7a03
Tx public key: 3d06c1aee73466e0dca3df2036315da61dd6ccdfa98e2007f1aee60e24a56532
Timestamp: 1758947853 Timestamp [UCT]: 2025-09-27 04:37:33 Age [y:d:h:m:s]: 00:042:03:20:07
Block: 1377347 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 30168 RingCT/type: yes/0
Extra: 013d06c1aee73466e0dca3df2036315da61dd6ccdfa98e2007f1aee60e24a56532021100000003a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4f361b98df2782089586a96965ad9d835d8e181edc0b6feca7d1b22e6a7a0c4c 0.600000000000 1865438 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": 1377357, "vin": [ { "gen": { "height": 1377347 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4f361b98df2782089586a96965ad9d835d8e181edc0b6feca7d1b22e6a7a0c4c" } } ], "extra": [ 1, 61, 6, 193, 174, 231, 52, 102, 224, 220, 163, 223, 32, 54, 49, 93, 166, 29, 214, 204, 223, 169, 142, 32, 7, 241, 174, 230, 14, 36, 165, 101, 50, 2, 17, 0, 0, 0, 3, 165, 220, 205, 121, 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