Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72471a1abd9500d85ce599e2057e37fb42f0140a8bf98b3b56bd4dc1ca4389dd

Tx prefix hash: c0f50bc681817d7ea58f0cf1dc996a840e9d6a72b8dfa6f2745a314e352952dc
Tx public key: ff72a456131d96ae6527aef94afb893f250d0a141275ae3f3a8b953f5ce41a0c
Timestamp: 1729604720 Timestamp [UCT]: 2024-10-22 13:45:20 Age [y:d:h:m:s]: 00:242:03:28:21
Block: 1137146 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 172745 RingCT/type: yes/0
Extra: 01ff72a456131d96ae6527aef94afb893f250d0a141275ae3f3a8b953f5ce41a0c021100000001a6b5e9fb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 78d38e336d7b1b5c41f4caa1edb838f64272c05182790ff3cdf08f418e051b80 0.600000000000 1620583 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": 1137156, "vin": [ { "gen": { "height": 1137146 } } ], "vout": [ { "amount": 600000000, "target": { "key": "78d38e336d7b1b5c41f4caa1edb838f64272c05182790ff3cdf08f418e051b80" } } ], "extra": [ 1, 255, 114, 164, 86, 19, 29, 150, 174, 101, 39, 174, 249, 74, 251, 137, 63, 37, 13, 10, 20, 18, 117, 174, 63, 58, 139, 149, 63, 92, 228, 26, 12, 2, 17, 0, 0, 0, 1, 166, 181, 233, 251, 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