Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b5b871afa7cd0cc906004305be135e8a3052331fab06163d1d1fde0199f18d1c

Tx prefix hash: a8f2029e338d64a823808932747f22dcf903b937e54a06eee350cd79376d8444
Tx public key: 12ce535da3ee4e9f6056ad2a543c1fbd4935bdbc347c3e0d4efa3ff8dc67c45d
Timestamp: 1723060776 Timestamp [UCT]: 2024-08-07 19:59:36 Age [y:d:h:m:s]: 00:199:18:48:12
Block: 1082926 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142634 RingCT/type: yes/0
Extra: 0112ce535da3ee4e9f6056ad2a543c1fbd4935bdbc347c3e0d4efa3ff8dc67c45d02110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e162f5846621be4a16e246eb5fcdf8d19b14f0599a5306aa8247ab30e2b83b7d 0.600000000000 1556761 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": 1082936, "vin": [ { "gen": { "height": 1082926 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e162f5846621be4a16e246eb5fcdf8d19b14f0599a5306aa8247ab30e2b83b7d" } } ], "extra": [ 1, 18, 206, 83, 93, 163, 238, 78, 159, 96, 86, 173, 42, 84, 60, 31, 189, 73, 53, 189, 188, 52, 124, 62, 13, 78, 250, 63, 248, 220, 103, 196, 93, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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