Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0b40c24d0bbe36373b942c184613d601caf66c2dc6b2496d1177976d1844f00d

Tx prefix hash: 10adc558151101c924e32f9feca69d2492bfb02695d5540f406a6a451f5f8949
Tx public key: b26699858dee3b57207ddfa72c86d0bcfb2ee817833e52d93f3ec63ed0e0f4f5
Timestamp: 1720464985 Timestamp [UCT]: 2024-07-08 18:56:25 Age [y:d:h:m:s]: 00:271:21:51:41
Block: 1061414 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 194258 RingCT/type: yes/0
Extra: 01b26699858dee3b57207ddfa72c86d0bcfb2ee817833e52d93f3ec63ed0e0f4f5021100000007e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: eff0598f0f51fe1a63448c00e5ac52b9de154918d50c1737920735f7d83705a5 0.600000000000 1531905 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": 1061424, "vin": [ { "gen": { "height": 1061414 } } ], "vout": [ { "amount": 600000000, "target": { "key": "eff0598f0f51fe1a63448c00e5ac52b9de154918d50c1737920735f7d83705a5" } } ], "extra": [ 1, 178, 102, 153, 133, 141, 238, 59, 87, 32, 125, 223, 167, 44, 134, 208, 188, 251, 46, 232, 23, 131, 62, 82, 217, 63, 62, 198, 62, 208, 224, 244, 245, 2, 17, 0, 0, 0, 7, 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