Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24ae5d4ee34d338c5c67bc565ea58599e175eab362e29baa9dd94f6af9071a1b

Tx prefix hash: bbe8ed25f68d809ec887cbe8ed508e438c5d0800f43140023668277da81ee84e
Tx public key: 611c1a6238fd42698f578ccae7c65187fc90e3bd4bf851af5e7a2a80f72425d2
Timestamp: 1765425608 Timestamp [UCT]: 2025-12-11 04:00:08 Age [y:d:h:m:s]: 00:024:12:33:48
Block: 1431018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 17580 RingCT/type: yes/0
Extra: 01611c1a6238fd42698f578ccae7c65187fc90e3bd4bf851af5e7a2a80f72425d2021100000003d6e19d7c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ed8ff35e5c7d2e76bd13c29efd04bc1aa9870f1c087d26f015a8efe144622393 0.600000000000 1919773 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": 1431028, "vin": [ { "gen": { "height": 1431018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ed8ff35e5c7d2e76bd13c29efd04bc1aa9870f1c087d26f015a8efe144622393" } } ], "extra": [ 1, 97, 28, 26, 98, 56, 253, 66, 105, 143, 87, 140, 202, 231, 198, 81, 135, 252, 144, 227, 189, 75, 248, 81, 175, 94, 122, 42, 128, 247, 36, 37, 210, 2, 17, 0, 0, 0, 3, 214, 225, 157, 124, 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