Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: fafbe32afa68ed3f19b08fe3ce151522c0e9c4db9da147e3b65923a69728dac0

Tx prefix hash: db40c8a94757c65d0d5742cfafd10cecaa1fca5b1f7a8eff1e12ef731d3e3a0a
Tx public key: ad13a4f13190a26449bdf9c5ac958d617a05c96b69ede73660cabfc69b021cd1
Timestamp: 1717244751 Timestamp [UCT]: 2024-06-01 12:25:51 Age [y:d:h:m:s]: 01:160:21:41:43
Block: 1034722 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 373574 RingCT/type: yes/0
Extra: 01ad13a4f13190a26449bdf9c5ac958d617a05c96b69ede73660cabfc69b021cd102110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5f08d830510b6acf70a6ec827ff9fc550627c16df2e86fd83705123adbe2b83 0.600000000000 1503241 of 15

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": 1034732, "vin": [ { "gen": { "height": 1034722 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5f08d830510b6acf70a6ec827ff9fc550627c16df2e86fd83705123adbe2b83" } } ], "extra": [ 1, 173, 19, 164, 241, 49, 144, 162, 100, 73, 189, 249, 197, 172, 149, 141, 97, 122, 5, 201, 107, 105, 237, 231, 54, 96, 202, 191, 198, 155, 2, 28, 209, 2, 17, 0, 0, 0, 2, 89, 218, 211, 245, 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