Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 22043d459549be175a36ad34b5133a215028ba8f65f2f7064de52313b2107ba3

Tx prefix hash: b33ddbaf3b2fbdd70228146d55a797f10ade95df76ef98f4771f37ef9a61f5a8
Tx public key: 30b15b96d931e15d9a1401d3faaf9ea60d8b975fd6e696ca9d5b326481e71015
Timestamp: 1700860609 Timestamp [UCT]: 2023-11-24 21:16:49 Age [y:d:h:m:s]: 01:097:20:59:53
Block: 898887 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 331087 RingCT/type: yes/0
Extra: 0130b15b96d931e15d9a1401d3faaf9ea60d8b975fd6e696ca9d5b326481e7101502110000000ffaf35c9c000000000000000000

1 output(s) for total of 0.645080937000 dcy

stealth address amount amount idx
00: 508def2e48a5aba79ff1aadb182b4e6194e1c84b2fd480d1aae3a361b68c7b9a 0.645080937000 1355324 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": 898897, "vin": [ { "gen": { "height": 898887 } } ], "vout": [ { "amount": 645080937, "target": { "key": "508def2e48a5aba79ff1aadb182b4e6194e1c84b2fd480d1aae3a361b68c7b9a" } } ], "extra": [ 1, 48, 177, 91, 150, 217, 49, 225, 93, 154, 20, 1, 211, 250, 175, 158, 166, 13, 139, 151, 95, 214, 230, 150, 202, 157, 91, 50, 100, 129, 231, 16, 21, 2, 17, 0, 0, 0, 15, 250, 243, 92, 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