Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b7a9501d081a271f2d5d6a7288f2fb317d8e10a9616fba8af9c9c539d27297cc

Tx prefix hash: f9cf30b478202291bf79b65a88721062c8af62cc29ee83239376c4d2e5bca7d8
Tx public key: d86f0a5d242ecd717248d7805191511b5d9b94e37680f84883e2945b62407790
Timestamp: 1671633947 Timestamp [UCT]: 2022-12-21 14:45:47 Age [y:d:h:m:s]: 02:111:01:23:01
Block: 657454 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 601070 RingCT/type: yes/0
Extra: 01d86f0a5d242ecd717248d7805191511b5d9b94e37680f84883e2945b624077900211000000017e406890000000000000000000

1 output(s) for total of 4.069883254000 dcy

stealth address amount amount idx
00: 73826d11998c08beec58974d6c939ecd667a7c004fd7c50d5c7aa28433991f46 4.069883254000 1098099 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": 657464, "vin": [ { "gen": { "height": 657454 } } ], "vout": [ { "amount": 4069883254, "target": { "key": "73826d11998c08beec58974d6c939ecd667a7c004fd7c50d5c7aa28433991f46" } } ], "extra": [ 1, 216, 111, 10, 93, 36, 46, 205, 113, 114, 72, 215, 128, 81, 145, 81, 27, 93, 155, 148, 227, 118, 128, 248, 72, 131, 226, 148, 91, 98, 64, 119, 144, 2, 17, 0, 0, 0, 1, 126, 64, 104, 144, 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