Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 982cb8797950d1e28011d9722762e56c0136db010a5a5df5c7b918fe22c9edf8

Tx prefix hash: d111503563fc1e7dfe30bc2205dec0b51dbc784e68bca3e21c9b2a0d69f43a68
Tx public key: 57039c56cc2507657b6180caef659b5a07269c9e8af063d4d710ac67da853595
Timestamp: 1672989536 Timestamp [UCT]: 2023-01-06 07:18:56 Age [y:d:h:m:s]: 01:331:13:23:06
Block: 668683 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 497987 RingCT/type: yes/0
Extra: 0157039c56cc2507657b6180caef659b5a07269c9e8af063d4d710ac67da85359502110000000133af99f4000000000000000000

1 output(s) for total of 3.735731003000 dcy

stealth address amount amount idx
00: def59d3f0db70b5c3259c4d9ae4279891c7dacbb7ac591df7dfb2244192371cc 3.735731003000 1109940 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": 668693, "vin": [ { "gen": { "height": 668683 } } ], "vout": [ { "amount": 3735731003, "target": { "key": "def59d3f0db70b5c3259c4d9ae4279891c7dacbb7ac591df7dfb2244192371cc" } } ], "extra": [ 1, 87, 3, 156, 86, 204, 37, 7, 101, 123, 97, 128, 202, 239, 101, 155, 90, 7, 38, 156, 158, 138, 240, 99, 212, 215, 16, 172, 103, 218, 133, 53, 149, 2, 17, 0, 0, 0, 1, 51, 175, 153, 244, 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