Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 757208083a9dc6073a8f2886ffa49f4b8993f546d52c5ca54196d06dd372fdd2

Tx prefix hash: 74d0856b2dfd6552da586d6973b8220e6ca9ceb678ab5ad746f8a91e2aaa7f85
Tx public key: a2d5354abff78c1cb168ee62c86e3336d82a9df829826a62bbb5a3eff813f54c
Timestamp: 1712070780 Timestamp [UCT]: 2024-04-02 15:13:00 Age [y:d:h:m:s]: 00:326:20:13:25
Block: 991786 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 233679 RingCT/type: yes/0
Extra: 01a2d5354abff78c1cb168ee62c86e3336d82a9df829826a62bbb5a3eff813f54c0211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2a0b93282f260d884062389151e6e9eec48863eb8f2555518a9ad2740b91819 0.600000000000 1452122 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": 991796, "vin": [ { "gen": { "height": 991786 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2a0b93282f260d884062389151e6e9eec48863eb8f2555518a9ad2740b91819" } } ], "extra": [ 1, 162, 213, 53, 74, 191, 247, 140, 28, 177, 104, 238, 98, 200, 110, 51, 54, 216, 42, 157, 248, 41, 130, 106, 98, 187, 181, 163, 239, 248, 19, 245, 76, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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