Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: de9aecd6cd17b8a899de7bf7c5d85ab9bff86eb92f72706bfb8acd315a1002b2

Tx prefix hash: 2da240c76dd26f73765d542f95d20ec726591b91b07652b60d63ada71b6404bb
Tx public key: ae21934da8e120e5bd44d0a62766b7ed79c3e8873a91d9cb4ad59a2974fd745b
Timestamp: 1750928219 Timestamp [UCT]: 2025-06-26 08:56:59 Age [y:d:h:m:s]: 00:145:14:14:35
Block: 1313076 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 102048 RingCT/type: yes/0
Extra: 01ae21934da8e120e5bd44d0a62766b7ed79c3e8873a91d9cb4ad59a2974fd745b021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 902dde5fa423ad2a12557cdd1ee0508a72958acc68f2e7449ca3012620379e9b 0.600000000000 1800713 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": 1313086, "vin": [ { "gen": { "height": 1313076 } } ], "vout": [ { "amount": 600000000, "target": { "key": "902dde5fa423ad2a12557cdd1ee0508a72958acc68f2e7449ca3012620379e9b" } } ], "extra": [ 1, 174, 33, 147, 77, 168, 225, 32, 229, 189, 68, 208, 166, 39, 102, 183, 237, 121, 195, 232, 135, 58, 145, 217, 203, 74, 213, 154, 41, 116, 253, 116, 91, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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