Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 441c8d911fbe637d38e2902bd2a5a0dd3fa3341f3cd078814b23df77681656a7

Tx prefix hash: 9bebc3e4c46c815f56a4f0c3a6e26ff0d71f7602c89e24f51c13895b138df1ef
Tx public key: 4380b74851eb4b7d7b28bff1b799562f2543c241df072501a29d92273394b20a
Timestamp: 1724042686 Timestamp [UCT]: 2024-08-19 04:44:46 Age [y:d:h:m:s]: 00:229:18:38:23
Block: 1091085 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 164077 RingCT/type: yes/0
Extra: 014380b74851eb4b7d7b28bff1b799562f2543c241df072501a29d92273394b20a021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 948176fdb21aa0337e7523168cc7f294fd6d3a9c1f35e7dc79cfbe0b6ca1b0d7 0.600000000000 1565710 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": 1091095, "vin": [ { "gen": { "height": 1091085 } } ], "vout": [ { "amount": 600000000, "target": { "key": "948176fdb21aa0337e7523168cc7f294fd6d3a9c1f35e7dc79cfbe0b6ca1b0d7" } } ], "extra": [ 1, 67, 128, 183, 72, 81, 235, 75, 125, 123, 40, 191, 241, 183, 153, 86, 47, 37, 67, 194, 65, 223, 7, 37, 1, 162, 157, 146, 39, 51, 148, 178, 10, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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