Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e320aa46ee449d6de0c08cb4fe8d96a40831ef6952fa69881fe9c2b614f04492

Tx prefix hash: f23a63e973b29053cf44a21edb823e4f8420fee6d87e87d7616f6232a2781d89
Tx public key: a8d72b584dae9d97828e6da18b50170877664ad535fb4c1e0b7b667f45aca712
Timestamp: 1756373061 Timestamp [UCT]: 2025-08-28 09:24:21 Age [y:d:h:m:s]: 00:073:22:13:18
Block: 1356190 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 52747 RingCT/type: yes/0
Extra: 01a8d72b584dae9d97828e6da18b50170877664ad535fb4c1e0b7b667f45aca7120211000000032609b3a0000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d3ca9d0136ed822cb4a21bcf43c9c875f77becc772b3fdc3e686b5bf1cd7bd0 0.600000000000 1844197 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": 1356200, "vin": [ { "gen": { "height": 1356190 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d3ca9d0136ed822cb4a21bcf43c9c875f77becc772b3fdc3e686b5bf1cd7bd0" } } ], "extra": [ 1, 168, 215, 43, 88, 77, 174, 157, 151, 130, 142, 109, 161, 139, 80, 23, 8, 119, 102, 74, 213, 53, 251, 76, 30, 11, 123, 102, 127, 69, 172, 167, 18, 2, 17, 0, 0, 0, 3, 38, 9, 179, 160, 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