Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b53e28a022dd1ebe832084e806d977dd0beb3ddf30ec5145418cec85d0ebcf13

Tx prefix hash: 557b2a16675607184b9363becea9ece6a52f9689961323fdec710c85a36cb0d1
Tx public key: dd0e1a5d791687328de8a549cccb629ec062d83bfa39d6c7df341322170913a4
Timestamp: 1682602508 Timestamp [UCT]: 2023-04-27 13:35:08 Age [y:d:h:m:s]: 01:350:21:12:06
Block: 747764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 512026 RingCT/type: yes/0
Extra: 01dd0e1a5d791687328de8a549cccb629ec062d83bfa39d6c7df341322170913a4021100000002e6d27f9c000000000000000000

1 output(s) for total of 2.043373058000 dcy

stealth address amount amount idx
00: 400d76c55895e20c3e2f5f3cc6b5f6751950cdcc2627a2ba95c57a11b1b1bc5e 2.043373058000 1195515 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": 747774, "vin": [ { "gen": { "height": 747764 } } ], "vout": [ { "amount": 2043373058, "target": { "key": "400d76c55895e20c3e2f5f3cc6b5f6751950cdcc2627a2ba95c57a11b1b1bc5e" } } ], "extra": [ 1, 221, 14, 26, 93, 121, 22, 135, 50, 141, 232, 165, 73, 204, 203, 98, 158, 192, 98, 216, 59, 250, 57, 214, 199, 223, 52, 19, 34, 23, 9, 19, 164, 2, 17, 0, 0, 0, 2, 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