Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c833f2a1d7e6cd5e329f74f502029936414ecf22e36c268d2442ac97524f8b4

Tx prefix hash: 259746c8870a1e8b10a63ee635a3df0a95ce9f9a01b87b3995d0f74904cdf40c
Tx public key: 90691dd6e8f45be0ff19526fcf8e7dfde5dd1f8d755c7a020b822982173e2f8b
Timestamp: 1639000128 Timestamp [UCT]: 2021-12-08 21:48:48 Age [y:d:h:m:s]: 03:067:23:43:51
Block: 391337 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 827304 RingCT/type: yes/0
Extra: 0190691dd6e8f45be0ff19526fcf8e7dfde5dd1f8d755c7a020b822982173e2f8b021100000020536c63bb000000000000000000

1 output(s) for total of 30.998339569000 dcy

stealth address amount amount idx
00: 305f6f2e8955964c4984b204a93a4baf8bf6bf94b10e6b872987766b6a03bb27 30.998339569000 787690 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": 391347, "vin": [ { "gen": { "height": 391337 } } ], "vout": [ { "amount": 30998339569, "target": { "key": "305f6f2e8955964c4984b204a93a4baf8bf6bf94b10e6b872987766b6a03bb27" } } ], "extra": [ 1, 144, 105, 29, 214, 232, 244, 91, 224, 255, 25, 82, 111, 207, 142, 125, 253, 229, 221, 31, 141, 117, 92, 122, 2, 11, 130, 41, 130, 23, 62, 47, 139, 2, 17, 0, 0, 0, 32, 83, 108, 99, 187, 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