Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fdc60ffd31ce8c683b7e1302277ebe47ad20e82be3d3185d1438b9b89f466d35

Tx prefix hash: d732c577c8f3137497338929182c9a7e94af351b9588d623fa413a85036e59de
Tx public key: 58a4334459745279ec3b8faeb9cb80996cd268b4cc92f8c5aa3a9a7f24e40f0b
Timestamp: 1738225163 Timestamp [UCT]: 2025-01-30 08:19:23 Age [y:d:h:m:s]: 00:139:04:06:44
Block: 1208228 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 99429 RingCT/type: yes/0
Extra: 0158a4334459745279ec3b8faeb9cb80996cd268b4cc92f8c5aa3a9a7f24e40f0b0211000000021f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8de6d6ec123874c220c3d39c67d2888c8d366679e8af5d9eb6d23472ae089042 0.600000000000 1694959 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": 1208238, "vin": [ { "gen": { "height": 1208228 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8de6d6ec123874c220c3d39c67d2888c8d366679e8af5d9eb6d23472ae089042" } } ], "extra": [ 1, 88, 164, 51, 68, 89, 116, 82, 121, 236, 59, 143, 174, 185, 203, 128, 153, 108, 210, 104, 180, 204, 146, 248, 197, 170, 58, 154, 127, 36, 228, 15, 11, 2, 17, 0, 0, 0, 2, 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