Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 652d0a303f6c01701d043af3103c9959674371a29520c040395b6f325827bd6c

Tx prefix hash: b22bac3c7f098510a1243b7489f19b4f1467b79400e1d3db9e674c40fcfc5280
Tx public key: 382d1c7af6d4ec2fbe4ac8261200094cf64426eb6df7b8d033c340decfc2478e
Timestamp: 1672861741 Timestamp [UCT]: 2023-01-04 19:49:01 Age [y:d:h:m:s]: 02:146:09:37:25
Block: 667632 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 626344 RingCT/type: yes/0
Extra: 01382d1c7af6d4ec2fbe4ac8261200094cf64426eb6df7b8d033c340decfc2478e02110000000475e3f0e9000000000000000000

1 output(s) for total of 3.765806472000 dcy

stealth address amount amount idx
00: e770367398d99cf0382588d9485dc8a6f176cdac57bcd0f5ac7cd2ab9a99c9a7 3.765806472000 1108847 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": 667642, "vin": [ { "gen": { "height": 667632 } } ], "vout": [ { "amount": 3765806472, "target": { "key": "e770367398d99cf0382588d9485dc8a6f176cdac57bcd0f5ac7cd2ab9a99c9a7" } } ], "extra": [ 1, 56, 45, 28, 122, 246, 212, 236, 47, 190, 74, 200, 38, 18, 0, 9, 76, 246, 68, 38, 235, 109, 247, 184, 208, 51, 195, 64, 222, 207, 194, 71, 142, 2, 17, 0, 0, 0, 4, 117, 227, 240, 233, 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