Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 668d37908e2394de6913f2fb318c1c724309b31498f3edfc7327be67251c0277

Tx prefix hash: b331004f74191702d78a1b39e78d98e7910b41214948f12e6e0d45382db9e974
Tx public key: 1bdf0a67d76c7aa8a849f058f4e7d5951aa0b584f29f1ad7cec8b4c4fbbb72b7
Timestamp: 1724483217 Timestamp [UCT]: 2024-08-24 07:06:57 Age [y:d:h:m:s]: 00:237:03:20:25
Block: 1094732 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 169353 RingCT/type: yes/0
Extra: 011bdf0a67d76c7aa8a849f058f4e7d5951aa0b584f29f1ad7cec8b4c4fbbb72b7021100000002e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 518a568500d163bb090116ab9b00362fdfaed5a40d9ec7c0acf0404192d7c3d5 0.600000000000 1569851 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": 1094742, "vin": [ { "gen": { "height": 1094732 } } ], "vout": [ { "amount": 600000000, "target": { "key": "518a568500d163bb090116ab9b00362fdfaed5a40d9ec7c0acf0404192d7c3d5" } } ], "extra": [ 1, 27, 223, 10, 103, 215, 108, 122, 168, 168, 73, 240, 88, 244, 231, 213, 149, 26, 160, 181, 132, 242, 159, 26, 215, 206, 200, 180, 196, 251, 187, 114, 183, 2, 17, 0, 0, 0, 2, 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