Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 288a44ad7f111ae4bbfc8ebc8d345404e2b8f67a07cb20e2d8a6d5520fd75f38

Tx prefix hash: f1ab083f74151a10dbb38bbdba138d1fa4633ad394066db77812569cecbc8874
Tx public key: eb2c76a57fa9a9f82628465096861c034fe6a886594f3498b2216b0ed924062c
Timestamp: 1750421199 Timestamp [UCT]: 2025-06-20 12:06:39 Age [y:d:h:m:s]: 00:152:20:16:24
Block: 1309039 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 107075 RingCT/type: yes/0
Extra: 01eb2c76a57fa9a9f82628465096861c034fe6a886594f3498b2216b0ed924062c02110000000dbf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9474ca1ac59e0ce3333699e21b3f1e9b1f039f449d2cae76b371c8b5013a3fb4 0.600000000000 1796654 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": 1309049, "vin": [ { "gen": { "height": 1309039 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9474ca1ac59e0ce3333699e21b3f1e9b1f039f449d2cae76b371c8b5013a3fb4" } } ], "extra": [ 1, 235, 44, 118, 165, 127, 169, 169, 248, 38, 40, 70, 80, 150, 134, 28, 3, 79, 230, 168, 134, 89, 79, 52, 152, 178, 33, 107, 14, 217, 36, 6, 44, 2, 17, 0, 0, 0, 13, 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