Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8de7623c9757c261a9b4c70ba5fcc1426d2e78676bc94a96b9b27138bb139eb7

Tx prefix hash: 60bbf23223fd398c371a28dc0ccc91ead654fbd140dbfce66a851071538a59ad
Tx public key: 3b556f21b256f5f1eb5ce28414c2b63236f4a9c449e2b12f778cb977d234a674
Timestamp: 1737111607 Timestamp [UCT]: 2025-01-17 11:00:07 Age [y:d:h:m:s]: 00:307:20:05:36
Block: 1199274 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 217504 RingCT/type: yes/0
Extra: 013b556f21b256f5f1eb5ce28414c2b63236f4a9c449e2b12f778cb977d234a6740211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7fe5db010ea5a1135c6eeed477afdc8112b4ce7d6da70d67a2a4553a1d29e235 0.600000000000 1685903 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": 1199284, "vin": [ { "gen": { "height": 1199274 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7fe5db010ea5a1135c6eeed477afdc8112b4ce7d6da70d67a2a4553a1d29e235" } } ], "extra": [ 1, 59, 85, 111, 33, 178, 86, 245, 241, 235, 92, 226, 132, 20, 194, 182, 50, 54, 244, 169, 196, 73, 226, 177, 47, 119, 140, 185, 119, 210, 52, 166, 116, 2, 17, 0, 0, 0, 3, 31, 10, 83, 235, 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