Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: faa74c754431cf4d0abe7c5b85374e9a0a90e21e20f004f2c19ea0a3aae4a630

Tx prefix hash: 8dc289243e7456779d9640defcdb4d276e62ee47a5be5bf6c2335981f3ad499a
Tx public key: 44df3092ddc6f99a1ce50df4e67e56dae78929e0f072236d1ce1d6ea4b630a6a
Timestamp: 1745349466 Timestamp [UCT]: 2025-04-22 19:17:46 Age [y:d:h:m:s]: 00:252:11:25:14
Block: 1267200 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 178224 RingCT/type: yes/0
Extra: 0144df3092ddc6f99a1ce50df4e67e56dae78929e0f072236d1ce1d6ea4b630a6a02110000000101491f88000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5d72935a8ef5667426710df732b3156a1d1dc96c42bf85a9f5f8622c787dd0ee 0.600000000000 1754427 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": 1267210, "vin": [ { "gen": { "height": 1267200 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5d72935a8ef5667426710df732b3156a1d1dc96c42bf85a9f5f8622c787dd0ee" } } ], "extra": [ 1, 68, 223, 48, 146, 221, 198, 249, 154, 28, 229, 13, 244, 230, 126, 86, 218, 231, 137, 41, 224, 240, 114, 35, 109, 28, 225, 214, 234, 75, 99, 10, 106, 2, 17, 0, 0, 0, 1, 1, 73, 31, 136, 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