Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: acec127f4385182a1bc4e6478e0a56403dfdb548418121b015bbacf2e4738efa

Tx prefix hash: 695a8f17f056408c080ff7db5723d01618178b6dc3504f333b89f803e3fa90a9
Tx public key: 0280eb87307a9a1ea2ab108a7ff36346f2d3e04a4fa3b675bc14e9d11eb5a921
Timestamp: 1699808602 Timestamp [UCT]: 2023-11-12 17:03:22 Age [y:d:h:m:s]: 01:208:15:04:31
Block: 890167 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 410331 RingCT/type: yes/0
Extra: 010280eb87307a9a1ea2ab108a7ff36346f2d3e04a4fa3b675bc14e9d11eb5a9210211000000014b8f5122000000000000000000

1 output(s) for total of 0.689457025000 dcy

stealth address amount amount idx
00: 557781a9840aa61b469d1b4ff8085ac513d2979f501a10b80af5766107572f52 0.689457025000 1346188 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": 890177, "vin": [ { "gen": { "height": 890167 } } ], "vout": [ { "amount": 689457025, "target": { "key": "557781a9840aa61b469d1b4ff8085ac513d2979f501a10b80af5766107572f52" } } ], "extra": [ 1, 2, 128, 235, 135, 48, 122, 154, 30, 162, 171, 16, 138, 127, 243, 99, 70, 242, 211, 224, 74, 79, 163, 182, 117, 188, 20, 233, 209, 30, 181, 169, 33, 2, 17, 0, 0, 0, 1, 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