Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 82c9467ff1d7a7627b5971879f6282bb8a2637989e89fdb1a2c967d128a94cf5

Tx prefix hash: 148fc71331ab659d06ccfce6dd97269c932208043634754ace99fb50df1e59b1
Tx public key: e8b6582b1a028064e94cc7522a0ac0fbc3b832dab762cfef9e05c5a0393b43fd
Timestamp: 1749203159 Timestamp [UCT]: 2025-06-06 09:45:59 Age [y:d:h:m:s]: 00:161:14:46:52
Block: 1299111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 113194 RingCT/type: yes/0
Extra: 01e8b6582b1a028064e94cc7522a0ac0fbc3b832dab762cfef9e05c5a0393b43fd021100000003bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4adce9c33ce2d37165fe7362bfae0ff4267a67b1aff6edf6e68e58c7b7fb1edf 0.600000000000 1786646 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": 1299121, "vin": [ { "gen": { "height": 1299111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4adce9c33ce2d37165fe7362bfae0ff4267a67b1aff6edf6e68e58c7b7fb1edf" } } ], "extra": [ 1, 232, 182, 88, 43, 26, 2, 128, 100, 233, 76, 199, 82, 42, 10, 192, 251, 195, 184, 50, 218, 183, 98, 207, 239, 158, 5, 197, 160, 57, 59, 67, 253, 2, 17, 0, 0, 0, 3, 191, 81, 178, 162, 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