Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ec1db63541ca9a793ae288301f4c5f63e36149626ef61fc335d7f9cfbc0fc88

Tx prefix hash: e3835540ce5d74b99db211b14c5d7415143beeab3d8346511f3c52d9b345610c
Tx public key: bd8e77e9e7f3f427aeb2eb7d98ddaf6656ae6a0dc738a66ed95a3a6dfb6b6a80
Timestamp: 1737462170 Timestamp [UCT]: 2025-01-21 12:22:50 Age [y:d:h:m:s]: 00:147:13:55:27
Block: 1202138 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 105217 RingCT/type: yes/0
Extra: 01bd8e77e9e7f3f427aeb2eb7d98ddaf6656ae6a0dc738a66ed95a3a6dfb6b6a800211000000061f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0e993372caf8e62cf87d716b24e031c8598af2c398b4ff037333f2ad36de9819 0.600000000000 1688797 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": 1202148, "vin": [ { "gen": { "height": 1202138 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0e993372caf8e62cf87d716b24e031c8598af2c398b4ff037333f2ad36de9819" } } ], "extra": [ 1, 189, 142, 119, 233, 231, 243, 244, 39, 174, 178, 235, 125, 152, 221, 175, 102, 86, 174, 106, 13, 199, 56, 166, 110, 217, 90, 58, 109, 251, 107, 106, 128, 2, 17, 0, 0, 0, 6, 31, 10, 83, 235, 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