Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72e929a89d2b5844c45cda45c56aa5940d2ed5f4753a100c9646f66697ad59df

Tx prefix hash: 7a2f48778afdff6eee52878f1fae620b3330b198964f8cf773150244c5de293b
Tx public key: 048f102961376531d1c43aa043a7b51f27e797e097e664d865235c52087db8ab
Timestamp: 1727224497 Timestamp [UCT]: 2024-09-25 00:34:57 Age [y:d:h:m:s]: 00:108:06:26:30
Block: 1117449 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 77418 RingCT/type: yes/0
Extra: 01048f102961376531d1c43aa043a7b51f27e797e097e664d865235c52087db8ab021100000006e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f970aad4aafd985c7ac07975e24cb721c11c20b0eb7a4ed9c35fb920f23b39b1 0.600000000000 1598292 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": 1117459, "vin": [ { "gen": { "height": 1117449 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f970aad4aafd985c7ac07975e24cb721c11c20b0eb7a4ed9c35fb920f23b39b1" } } ], "extra": [ 1, 4, 143, 16, 41, 97, 55, 101, 49, 209, 196, 58, 160, 67, 167, 181, 31, 39, 231, 151, 224, 151, 230, 100, 216, 101, 35, 92, 82, 8, 125, 184, 171, 2, 17, 0, 0, 0, 6, 233, 20, 221, 21, 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