Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9abadfc95a90c7f5b292ae44b5689357ab5d11ed20d6344966be4f92e88889a9

Tx prefix hash: 4978168a6e5b2a112d8da6fed3a1eff5a5d2a82d671f5fd62aa8d1270b51d897
Tx public key: 68b4412072daedd6880e63433ab8fb571f3daecadbe3d14b514f4c3d35b05cc5
Timestamp: 1644489378 Timestamp [UCT]: 2022-02-10 10:36:18 Age [y:d:h:m:s]: 03:082:19:42:04
Block: 435640 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 839045 RingCT/type: yes/0
Extra: 0168b4412072daedd6880e63433ab8fb571f3daecadbe3d14b514f4c3d35b05cc502110000000f2e6b1fd5000000000000000000

1 output(s) for total of 22.107729242000 dcy

stealth address amount amount idx
00: dd776c3d7e44b44a35bf9c74f4ccb4a8f10cf46b36da81e931a3e2d1e48aec65 22.107729242000 846863 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": 435650, "vin": [ { "gen": { "height": 435640 } } ], "vout": [ { "amount": 22107729242, "target": { "key": "dd776c3d7e44b44a35bf9c74f4ccb4a8f10cf46b36da81e931a3e2d1e48aec65" } } ], "extra": [ 1, 104, 180, 65, 32, 114, 218, 237, 214, 136, 14, 99, 67, 58, 184, 251, 87, 31, 61, 174, 202, 219, 227, 209, 75, 81, 79, 76, 61, 53, 176, 92, 197, 2, 17, 0, 0, 0, 15, 46, 107, 31, 213, 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