Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f58ac741f0fd0101894c49e64dc19e8d57332cbfa0bb86914459bbe379724075

Tx prefix hash: 633b7449aba2f3e1e887a5a92a8ddf48e9c5fa7b3285a7bfd18dbf6ace6781f2
Tx public key: 1b1f60ce41d6b6e20b4d5fb2fc7bc6cfb01bff61c9ec29fd5a58aaf0e8018bcf
Timestamp: 1694879471 Timestamp [UCT]: 2023-09-16 15:51:11 Age [y:d:h:m:s]: 01:243:16:14:27
Block: 849478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 435277 RingCT/type: yes/0
Extra: 011b1f60ce41d6b6e20b4d5fb2fc7bc6cfb01bff61c9ec29fd5a58aaf0e8018bcf0211000000014b8f5122000000000000000000

1 output(s) for total of 0.940430722000 dcy

stealth address amount amount idx
00: ca35d91f373062ab311a94d67b3ab642bc29390411a034dccbd259dd56034542 0.940430722000 1303144 of 0

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": 849488, "vin": [ { "gen": { "height": 849478 } } ], "vout": [ { "amount": 940430722, "target": { "key": "ca35d91f373062ab311a94d67b3ab642bc29390411a034dccbd259dd56034542" } } ], "extra": [ 1, 27, 31, 96, 206, 65, 214, 182, 226, 11, 77, 95, 178, 252, 123, 198, 207, 176, 27, 255, 97, 201, 236, 41, 253, 90, 88, 170, 240, 232, 1, 139, 207, 2, 17, 0, 0, 0, 1, 75, 143, 81, 34, 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