Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e020476c78bb5751a0ca7d94c1f99888a5893a5c9941ff481438e3bd57960544

Tx prefix hash: b44a56bc7cfdd249d5dca8fc1c73b52ebd6f72edc563aa57483cb3cd03bd2215
Tx public key: 7a6fbf9a794360c0de85a4b536a8d75dcd09051ed63994c78f5fc187dc6ed593
Timestamp: 1743775765 Timestamp [UCT]: 2025-04-04 14:09:25 Age [y:d:h:m:s]: 00:229:17:52:04
Block: 1254174 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 161931 RingCT/type: yes/0
Extra: 017a6fbf9a794360c0de85a4b536a8d75dcd09051ed63994c78f5fc187dc6ed593021100000006a2ed016b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2031c7e7b4a7265b8a2ebcac0bbb77c26a4089eb1fcdf1f2fd665a6ed0545f9d 0.600000000000 1741255 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": 1254184, "vin": [ { "gen": { "height": 1254174 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2031c7e7b4a7265b8a2ebcac0bbb77c26a4089eb1fcdf1f2fd665a6ed0545f9d" } } ], "extra": [ 1, 122, 111, 191, 154, 121, 67, 96, 192, 222, 133, 164, 181, 54, 168, 215, 93, 205, 9, 5, 30, 214, 57, 148, 199, 143, 95, 193, 135, 220, 110, 213, 147, 2, 17, 0, 0, 0, 6, 162, 237, 1, 107, 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