Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ba002332055abe43896f4a8fd25d5ddd1486cfa43e6b42d471d6a5681f721081

Tx prefix hash: 9d7f893c01ac2e4788f08bfb06250f5ce7df0c93f5a7c39c6e9f4b6bf2f7ed37
Tx public key: aa1fbd868e73713108825b2aa652d75570fa504ad4ad82c9f1915b020aff6c0a
Timestamp: 1675146778 Timestamp [UCT]: 2023-01-31 06:32:58 Age [y:d:h:m:s]: 01:294:05:57:02
Block: 686574 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 471240 RingCT/type: yes/0
Extra: 01aa1fbd868e73713108825b2aa652d75570fa504ad4ad82c9f1915b020aff6c0a02110000000333af99f4000000000000000000

1 output(s) for total of 3.259081796000 dcy

stealth address amount amount idx
00: 95089897769f540fd0c923d1a85b197b49f77dc310f04e8931ce4248a38ce107 3.259081796000 1129075 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": 686584, "vin": [ { "gen": { "height": 686574 } } ], "vout": [ { "amount": 3259081796, "target": { "key": "95089897769f540fd0c923d1a85b197b49f77dc310f04e8931ce4248a38ce107" } } ], "extra": [ 1, 170, 31, 189, 134, 142, 115, 113, 49, 8, 130, 91, 42, 166, 82, 215, 85, 112, 250, 80, 74, 212, 173, 130, 201, 241, 145, 91, 2, 10, 255, 108, 10, 2, 17, 0, 0, 0, 3, 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