Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 517a58b88bfffc303e5cce5037945febe7a414c576efa681652463710d69069a

Tx prefix hash: 5618c584324db1a43847bce93191c1e3bedb4cf154067996c2cdef0d05fe54c5
Tx public key: d0201ea744c5538e6b96ae1fa0b5be67e1f4a6c7ac89626a734e943763194e02
Timestamp: 1672903135 Timestamp [UCT]: 2023-01-05 07:18:55 Age [y:d:h:m:s]: 02:304:02:11:05
Block: 667955 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 736745 RingCT/type: yes/0
Extra: 01d0201ea744c5538e6b96ae1fa0b5be67e1f4a6c7ac89626a734e943763194e02021100000006e6d27f9c000000000000000000

1 output(s) for total of 3.756537806000 dcy

stealth address amount amount idx
00: 549292aa6ca73ac99c5c96a016bbcdafe296adfac4f3543954fe68adca755983 3.756537806000 1109178 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": 667965, "vin": [ { "gen": { "height": 667955 } } ], "vout": [ { "amount": 3756537806, "target": { "key": "549292aa6ca73ac99c5c96a016bbcdafe296adfac4f3543954fe68adca755983" } } ], "extra": [ 1, 208, 32, 30, 167, 68, 197, 83, 142, 107, 150, 174, 31, 160, 181, 190, 103, 225, 244, 166, 199, 172, 137, 98, 106, 115, 78, 148, 55, 99, 25, 78, 2, 2, 17, 0, 0, 0, 6, 230, 210, 127, 156, 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