Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fc547560572e6396311ff08fdfd4069109ae59156793de1eeb9736f555ffc270

Tx prefix hash: 64e1e08f94decf5d6503e94e25bef2b8ec5a6de84a43ef03dcc213c674d33d5b
Tx public key: 4050ea2655f56f1bd84b6c495ebf4008697c4bea985a558f441ad7afae039db3
Timestamp: 1721059431 Timestamp [UCT]: 2024-07-15 16:03:51 Age [y:d:h:m:s]: 00:261:07:41:04
Block: 1066356 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 186662 RingCT/type: yes/0
Extra: 014050ea2655f56f1bd84b6c495ebf4008697c4bea985a558f441ad7afae039db3021100000001e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 400dc79bdfebf3e35f5c81ecd3d96e0d3dc2a11df7a7d07bc3e54f9c613e68d3 0.600000000000 1536929 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": 1066366, "vin": [ { "gen": { "height": 1066356 } } ], "vout": [ { "amount": 600000000, "target": { "key": "400dc79bdfebf3e35f5c81ecd3d96e0d3dc2a11df7a7d07bc3e54f9c613e68d3" } } ], "extra": [ 1, 64, 80, 234, 38, 85, 245, 111, 27, 216, 75, 108, 73, 94, 191, 64, 8, 105, 124, 75, 234, 152, 90, 85, 143, 68, 26, 215, 175, 174, 3, 157, 179, 2, 17, 0, 0, 0, 1, 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