Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 56548504bba4f7558d35d313c370dea19cca2e7c5ca9a222514c0756e0e68bf3

Tx prefix hash: 4e08cea31d4f275c6d87d74431edfd8e4c06283ce60cc0d8f2c198ec5df503c7
Tx public key: ee535493e1b38392994161296c4e609b98d9d538043a24021423dcd19d9301cb
Timestamp: 1681683658 Timestamp [UCT]: 2023-04-16 22:20:58 Age [y:d:h:m:s]: 01:315:05:01:24
Block: 740130 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 486527 RingCT/type: yes/0
Extra: 01ee535493e1b38392994161296c4e609b98d9d538043a24021423dcd19d9301cb021100000001faf35c9c000000000000000000

1 output(s) for total of 2.165919369000 dcy

stealth address amount amount idx
00: 1e0e2e5f932e543105a6bcadd126b09f116411fa9eef98f2d638369716d7c66f 2.165919369000 1187011 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": 740140, "vin": [ { "gen": { "height": 740130 } } ], "vout": [ { "amount": 2165919369, "target": { "key": "1e0e2e5f932e543105a6bcadd126b09f116411fa9eef98f2d638369716d7c66f" } } ], "extra": [ 1, 238, 83, 84, 147, 225, 179, 131, 146, 153, 65, 97, 41, 108, 78, 96, 155, 152, 217, 213, 56, 4, 58, 36, 2, 20, 35, 220, 209, 157, 147, 1, 203, 2, 17, 0, 0, 0, 1, 250, 243, 92, 156, 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