Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7566a1be5149201ffdb95b0f9b4b3abf97a571c8e20269330a3690a966238e17

Tx prefix hash: cc0b67409c3230b7efc48cebeac041cd37ab7b6504918766d7fab868bad3e7a6
Tx public key: d4ec91501a504ec8040d3a1f4bf824e56c0f2089a6742e509ada9ff1618e196f
Timestamp: 1731294343 Timestamp [UCT]: 2024-11-11 03:05:43 Age [y:d:h:m:s]: 00:197:15:43:08
Block: 1151111 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 141115 RingCT/type: yes/0
Extra: 01d4ec91501a504ec8040d3a1f4bf824e56c0f2089a6742e509ada9ff1618e196f0211000000031f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5264c7a88e5e4d933932e37e6ff1334e38a2cbcb7c51562e788ef26d88069853 0.600000000000 1636574 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": 1151121, "vin": [ { "gen": { "height": 1151111 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5264c7a88e5e4d933932e37e6ff1334e38a2cbcb7c51562e788ef26d88069853" } } ], "extra": [ 1, 212, 236, 145, 80, 26, 80, 78, 200, 4, 13, 58, 31, 75, 248, 36, 229, 108, 15, 32, 137, 166, 116, 46, 80, 154, 218, 159, 241, 97, 142, 25, 111, 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