Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3f04d7d05eebdf2ee518a53a61881b2f17bf623640a775cc51073d9a2629b811

Tx prefix hash: 827f49d2d5e3823ca3c5a8a2c73f790b1c72da9c502657c3345cd9b41943b658
Tx public key: 497b5ad89344d623bb9b7e556027b042e81f2c098f0ee743ac7cff6f48f1f666
Timestamp: 1698301572 Timestamp [UCT]: 2023-10-26 06:26:12 Age [y:d:h:m:s]: 01:202:15:50:32
Block: 877888 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 405847 RingCT/type: yes/0
Extra: 01497b5ad89344d623bb9b7e556027b042e81f2c098f0ee743ac7cff6f48f1f6660211000000034b8f5122000000000000000000

1 output(s) for total of 0.757168683000 dcy

stealth address amount amount idx
00: 2adfd8a479af9bd1486f694bfbd16c5f020955dba04a5d5492e5430564d3e732 0.757168683000 1333284 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": 877898, "vin": [ { "gen": { "height": 877888 } } ], "vout": [ { "amount": 757168683, "target": { "key": "2adfd8a479af9bd1486f694bfbd16c5f020955dba04a5d5492e5430564d3e732" } } ], "extra": [ 1, 73, 123, 90, 216, 147, 68, 214, 35, 187, 155, 126, 85, 96, 39, 176, 66, 232, 31, 44, 9, 143, 14, 231, 67, 172, 124, 255, 111, 72, 241, 246, 102, 2, 17, 0, 0, 0, 3, 75, 143, 81, 34, 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