Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f33294fbf781c9cee27c2feca37b074d45379712e7a3904df660263c917029cd

Tx prefix hash: 74b7d365c0ff90f16b5bc516fc1bb79e1672fa1a3ece2a0acc9f544e02547dc5
Tx public key: bb712bedb41adb8c907273042f4ad49ac14708ea4baca1aa6770d2d43374ccc7
Timestamp: 1751248428 Timestamp [UCT]: 2025-06-30 01:53:48 Age [y:d:h:m:s]: 00:132:14:40:09
Block: 1315538 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 92954 RingCT/type: yes/0
Extra: 01bb712bedb41adb8c907273042f4ad49ac14708ea4baca1aa6770d2d43374ccc70211000000018368266d000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e2de3d324177e3b4c6c851b28ddcd30f50671fa7987687e6c6bbc29291f241fb 0.600000000000 1803193 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": 1315548, "vin": [ { "gen": { "height": 1315538 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e2de3d324177e3b4c6c851b28ddcd30f50671fa7987687e6c6bbc29291f241fb" } } ], "extra": [ 1, 187, 113, 43, 237, 180, 26, 219, 140, 144, 114, 115, 4, 47, 74, 212, 154, 193, 71, 8, 234, 75, 172, 161, 170, 103, 112, 210, 212, 51, 116, 204, 199, 2, 17, 0, 0, 0, 1, 131, 104, 38, 109, 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