Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6909a2faee769f853c9f858046340883b36b86b9a7c099c0ef290073bf7cf8e

Tx prefix hash: 5b75c297076c12bf0c5341c9a167be4c24f48697aec604fc58f2e5db548fa049
Tx public key: 44660e63603759d041e58b478d09dc74f57dda0c4d8f64e3cecd1c6cb06084bd
Timestamp: 1709833346 Timestamp [UCT]: 2024-03-07 17:42:26 Age [y:d:h:m:s]: 00:313:09:34:59
Block: 973277 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 224330 RingCT/type: yes/0
Extra: 0144660e63603759d041e58b478d09dc74f57dda0c4d8f64e3cecd1c6cb06084bd02110000000152d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0fb3d35a41095a3286a3354349386b673581d22ca80a65f9c2e0bfac1b0a1b50 0.600000000000 1433212 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": 973287, "vin": [ { "gen": { "height": 973277 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0fb3d35a41095a3286a3354349386b673581d22ca80a65f9c2e0bfac1b0a1b50" } } ], "extra": [ 1, 68, 102, 14, 99, 96, 55, 89, 208, 65, 229, 139, 71, 141, 9, 220, 116, 245, 125, 218, 12, 77, 143, 100, 227, 206, 205, 28, 108, 176, 96, 132, 189, 2, 17, 0, 0, 0, 1, 82, 212, 126, 148, 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