Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2b0e6a86b92295d24edf0df79891f0e1c713fa1f68ca16e150c1756edd2ee245

Tx prefix hash: 2d463da372767a3ff88704b119beaa7ebf306cce9c7d200425c34717b88ee31e
Tx public key: 561198e30e82b026a9f3dc93844c67459c2dafac2994cb79a1ff4f9c044e9f6e
Timestamp: 1581213201 Timestamp [UCT]: 2020-02-09 01:53:21 Age [y:d:h:m:s]: 04:271:08:52:05
Block: 60974 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1086064 RingCT/type: yes/0
Extra: 01561198e30e82b026a9f3dc93844c67459c2dafac2994cb79a1ff4f9c044e9f6e0211000000164943cd9f000000000000000000

1 output(s) for total of 385.450526648000 dcy

stealth address amount amount idx
00: 41b877fde2c2ecd3b49d7fd6b97f617a4c41958da3a4ee86c0bcb38135aa0123 385.450526648000 112401 of 0

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": 60984, "vin": [ { "gen": { "height": 60974 } } ], "vout": [ { "amount": 385450526648, "target": { "key": "41b877fde2c2ecd3b49d7fd6b97f617a4c41958da3a4ee86c0bcb38135aa0123" } } ], "extra": [ 1, 86, 17, 152, 227, 14, 130, 176, 38, 169, 243, 220, 147, 132, 76, 103, 69, 156, 45, 175, 172, 41, 148, 203, 121, 161, 255, 79, 156, 4, 78, 159, 110, 2, 17, 0, 0, 0, 22, 73, 67, 205, 159, 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