Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 239531f841c0029a92443e49ff29bc97af5ac2191b821aceab5d89ae5ac699e2

Tx prefix hash: 8de889fc5329b5ddea1bb9ba7cc13b2753fd53a1b4fb5f7472682a541f9c2a2b
Tx public key: 351bef1c1065e7fa43f328a3189e461eee252510ff9713c2b2a8d5b3482050ee
Timestamp: 1704188608 Timestamp [UCT]: 2024-01-02 09:43:28 Age [y:d:h:m:s]: 01:097:03:47:37
Block: 926458 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 330548 RingCT/type: yes/0
Extra: 01351bef1c1065e7fa43f328a3189e461eee252510ff9713c2b2a8d5b3482050ee0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a52cdda58202f8e5eec1b6fdf6e742eaa3dacfc87a9bdd814650e13680c77275 0.600000000000 1384242 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": 926468, "vin": [ { "gen": { "height": 926458 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a52cdda58202f8e5eec1b6fdf6e742eaa3dacfc87a9bdd814650e13680c77275" } } ], "extra": [ 1, 53, 27, 239, 28, 16, 101, 231, 250, 67, 243, 40, 163, 24, 158, 70, 30, 238, 37, 37, 16, 255, 151, 19, 194, 178, 168, 213, 179, 72, 32, 80, 238, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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