Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b460f584be0520b86b974ae58ca743df627bbe7efa245c018137ef29285a0919

Tx prefix hash: a302065c80063df2f3f06f64bddd3617e9deac1e9c692dd7b7967962cb9c2fbd
Tx public key: 547c8204ff871c7544a81e0a1b564943e083ca235cb2b199ae92f27396c082e1
Timestamp: 1672694234 Timestamp [UCT]: 2023-01-02 21:17:14 Age [y:d:h:m:s]: 02:096:13:07:25
Block: 666235 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 590679 RingCT/type: yes/0
Extra: 01547c8204ff871c7544a81e0a1b564943e083ca235cb2b199ae92f27396c082e102110000000152542ceb000000000000000000

1 output(s) for total of 3.806158244000 dcy

stealth address amount amount idx
00: 203419ee9924340783c3532220ae203b2c96bce984c77724f6cf92c6e106a158 3.806158244000 1107338 of 0

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": 666245, "vin": [ { "gen": { "height": 666235 } } ], "vout": [ { "amount": 3806158244, "target": { "key": "203419ee9924340783c3532220ae203b2c96bce984c77724f6cf92c6e106a158" } } ], "extra": [ 1, 84, 124, 130, 4, 255, 135, 28, 117, 68, 168, 30, 10, 27, 86, 73, 67, 224, 131, 202, 35, 92, 178, 177, 153, 174, 146, 242, 115, 150, 192, 130, 225, 2, 17, 0, 0, 0, 1, 82, 84, 44, 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