Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2ce093cefa9dbd5e271a89833996021add31dd321c6d8c63bcc3dc7c8d7d480a

Tx prefix hash: b9c37d053ee2f99fa4f61e0c3c4db47d0f6cd477bdc96df1d0661f0acc2a4a23
Tx public key: 2df40ac6f2ee79dfb45aebd2d83eeffe2cf6815dc56396aa65b59a06864c05f8
Timestamp: 1750955985 Timestamp [UCT]: 2025-06-26 16:39:45 Age [y:d:h:m:s]: 00:147:21:59:57
Block: 1313291 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 103721 RingCT/type: yes/0
Extra: 012df40ac6f2ee79dfb45aebd2d83eeffe2cf6815dc56396aa65b59a06864c05f8021100000002a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f8a162f5a1a631ee56ab85e759a8b361c48326ea609a0e8681ace2ae499bce8e 0.600000000000 1800930 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": 1313301, "vin": [ { "gen": { "height": 1313291 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f8a162f5a1a631ee56ab85e759a8b361c48326ea609a0e8681ace2ae499bce8e" } } ], "extra": [ 1, 45, 244, 10, 198, 242, 238, 121, 223, 180, 90, 235, 210, 216, 62, 239, 254, 44, 246, 129, 93, 197, 99, 150, 170, 101, 181, 154, 6, 134, 76, 5, 248, 2, 17, 0, 0, 0, 2, 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