Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 40568e5abdcbf59f4a54a5fbf539cc53f0ec6eca7ecee9ebd7cddb0f0bc85fb3

Tx prefix hash: a33f63ed2cc9aaf2b4eb7af3226070d3a64b4cb89ffb504ad3b14ca71da0bb5c
Tx public key: 0d0f8f9bbb4ea13d7cf70258cf6d4b1c4a9ae941c8762c1429a503a1b19c49eb
Timestamp: 1705723312 Timestamp [UCT]: 2024-01-20 04:01:52 Age [y:d:h:m:s]: 01:094:06:06:38
Block: 939160 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 328479 RingCT/type: yes/0
Extra: 010d0f8f9bbb4ea13d7cf70258cf6d4b1c4a9ae941c8762c1429a503a1b19c49eb0211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 989e5a15cb45c32910b19c8203391922168f9ca3d881389fd9ac87c69f1b3781 0.600000000000 1397246 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": 939170, "vin": [ { "gen": { "height": 939160 } } ], "vout": [ { "amount": 600000000, "target": { "key": "989e5a15cb45c32910b19c8203391922168f9ca3d881389fd9ac87c69f1b3781" } } ], "extra": [ 1, 13, 15, 143, 155, 187, 78, 161, 61, 124, 247, 2, 88, 207, 109, 75, 28, 74, 154, 233, 65, 200, 118, 44, 20, 41, 165, 3, 161, 177, 156, 73, 235, 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