Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d789d40480a6bded7e2fb40d426220d2d4e288b325edc20f98bae444c7c5bc2c

Tx prefix hash: c7f1a06144024ac787b1fa5dd7d4aa1ea17272790bd08eca7849699bb85e2e7a
Tx public key: 4e9d56fa3a6ad35db0d7f553112388fd20dd72b46d764036ee03a6bba10e0d64
Timestamp: 1755085289 Timestamp [UCT]: 2025-08-13 11:41:29 Age [y:d:h:m:s]: 00:139:07:47:03
Block: 1346036 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99051 RingCT/type: yes/0
Extra: 014e9d56fa3a6ad35db0d7f553112388fd20dd72b46d764036ee03a6bba10e0d64021100000004d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 623e07e50a5813b044856c7e769fbd6641caba39e127e4cf95da1f6235ab5d23 0.600000000000 1833933 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": 1346046, "vin": [ { "gen": { "height": 1346036 } } ], "vout": [ { "amount": 600000000, "target": { "key": "623e07e50a5813b044856c7e769fbd6641caba39e127e4cf95da1f6235ab5d23" } } ], "extra": [ 1, 78, 157, 86, 250, 58, 106, 211, 93, 176, 215, 245, 83, 17, 35, 136, 253, 32, 221, 114, 180, 109, 118, 64, 54, 238, 3, 166, 187, 161, 14, 13, 100, 2, 17, 0, 0, 0, 4, 216, 231, 210, 65, 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