Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: af6c78999b9043e7e0b870580e6dc9fec37fff7d1c1e1b3de81619e800fe2075

Tx prefix hash: 89240b43552a0e3e2965ec9b6e0e2c31d83c064f930229b7cb978410306256b6
Tx public key: dfa3a5d85bf6e350d3da357f8527ff3f6aa6280ca5b126e1e27c5a4f059fd0f6
Timestamp: 1707664376 Timestamp [UCT]: 2024-02-11 15:12:56 Age [y:d:h:m:s]: 01:062:01:12:57
Block: 955278 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 305411 RingCT/type: yes/0
Extra: 01dfa3a5d85bf6e350d3da357f8527ff3f6aa6280ca5b126e1e27c5a4f059fd0f602110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6ff41602cb38fcdf33de4e3ccfce17d44268d3b580b1368c0ef97ba5a2c57d01 0.600000000000 1414564 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": 955288, "vin": [ { "gen": { "height": 955278 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6ff41602cb38fcdf33de4e3ccfce17d44268d3b580b1368c0ef97ba5a2c57d01" } } ], "extra": [ 1, 223, 163, 165, 216, 91, 246, 227, 80, 211, 218, 53, 127, 133, 39, 255, 63, 106, 166, 40, 12, 165, 177, 38, 225, 226, 124, 90, 79, 5, 159, 208, 246, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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