Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7b69f4fb17d8dcc9b7369a29dfea63293ee6ae3a3cdd043c38639fbeb567eff4

Tx prefix hash: 51c0fc243df409bf013e7caf4a66a6ca551474e8f3bd65f778fd5d32e87386d2
Tx public key: 14d9f48241d0bdc3f88b5d9f643be8f4f086ed830b675bc3a31b608803a546c2
Timestamp: 1706540313 Timestamp [UCT]: 2024-01-29 14:58:33 Age [y:d:h:m:s]: 01:296:04:14:09
Block: 945943 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 470495 RingCT/type: yes/0
Extra: 0114d9f48241d0bdc3f88b5d9f643be8f4f086ed830b675bc3a31b608803a546c202110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0d25519a3ae527db2431e324cbf3299697e83d40d919e8bf9c33b539931c940b 0.600000000000 1404273 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": 945953, "vin": [ { "gen": { "height": 945943 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0d25519a3ae527db2431e324cbf3299697e83d40d919e8bf9c33b539931c940b" } } ], "extra": [ 1, 20, 217, 244, 130, 65, 208, 189, 195, 248, 139, 93, 159, 100, 59, 232, 244, 240, 134, 237, 131, 11, 103, 91, 195, 163, 27, 96, 136, 3, 165, 70, 194, 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