Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c3d47e22cdbfefc7e152ed166e6783f0491c0892939a4363713999b2113171ef

Tx prefix hash: 556f254b897c7586e57e817a52bd6a8712248221839187ac94ec35f58d863c5a
Tx public key: 8afd05a554c9f51c83d268a73a564b8a48edcfad381ee525ebf3a2d4bb078260
Timestamp: 1699765926 Timestamp [UCT]: 2023-11-12 05:12:06 Age [y:d:h:m:s]: 01:141:22:03:49
Block: 889814 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 362592 RingCT/type: yes/0
Extra: 018afd05a554c9f51c83d268a73a564b8a48edcfad381ee525ebf3a2d4bb07826002110000000274c3735f000000000000000000

1 output(s) for total of 0.691316364000 dcy

stealth address amount amount idx
00: 57f6019ae7e236d4501c354afe54bb2e19bd5d56286819ef60e9c38d0ae38a90 0.691316364000 1345831 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": 889824, "vin": [ { "gen": { "height": 889814 } } ], "vout": [ { "amount": 691316364, "target": { "key": "57f6019ae7e236d4501c354afe54bb2e19bd5d56286819ef60e9c38d0ae38a90" } } ], "extra": [ 1, 138, 253, 5, 165, 84, 201, 245, 28, 131, 210, 104, 167, 58, 86, 75, 138, 72, 237, 207, 173, 56, 30, 229, 37, 235, 243, 162, 212, 187, 7, 130, 96, 2, 17, 0, 0, 0, 2, 116, 195, 115, 95, 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