Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b026886cab566b24795a58d089883044d83be4c3d7661fed3382723b78290db

Tx prefix hash: 134bffe02029cb50e10fe74c27e05bce0338f3c78960c454dc75a06501424e62
Tx public key: 4dbb8f32c8916c9597dc4f0c28df7381c9594fe5f80a7c7872919c99c69f32cb
Timestamp: 1657145338 Timestamp [UCT]: 2022-07-06 22:08:58 Age [y:d:h:m:s]: 02:110:13:16:00
Block: 538157 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 600356 RingCT/type: yes/0
Extra: 014dbb8f32c8916c9597dc4f0c28df7381c9594fe5f80a7c7872919c99c69f32cb0211000000014da16a3a000000000000000000

1 output(s) for total of 10.112594873000 dcy

stealth address amount amount idx
00: 0d3d54e13ad1e3531ba1ab72c16aa0e902e312a0bdbf0181831ec58aa05874ce 10.112594873000 968122 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": 538167, "vin": [ { "gen": { "height": 538157 } } ], "vout": [ { "amount": 10112594873, "target": { "key": "0d3d54e13ad1e3531ba1ab72c16aa0e902e312a0bdbf0181831ec58aa05874ce" } } ], "extra": [ 1, 77, 187, 143, 50, 200, 145, 108, 149, 151, 220, 79, 12, 40, 223, 115, 129, 201, 89, 79, 229, 248, 10, 124, 120, 114, 145, 156, 153, 198, 159, 50, 203, 2, 17, 0, 0, 0, 1, 77, 161, 106, 58, 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