Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7233c86d25e216e1dce65cd87e2d30229dc638ff1aee7ba61d01acd0e81d1fd

Tx prefix hash: 30ca7eb5ae2ebcd005e996d67cf7287adaf0a7a9adbb734020e9e3fcfaa54e3c
Tx public key: 34b6efe5adfe883870ed1c8f74c31947239422884d057d6776695a25e89555c7
Timestamp: 1682843645 Timestamp [UCT]: 2023-04-30 08:34:05 Age [y:d:h:m:s]: 02:270:05:33:28
Block: 749764 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 712888 RingCT/type: yes/0
Extra: 0134b6efe5adfe883870ed1c8f74c31947239422884d057d6776695a25e89555c702110000000575e3f0e9000000000000000000

1 output(s) for total of 2.012430217000 dcy

stealth address amount amount idx
00: 7287d44c5830be4ac32fd294d33aae29a4a6af65f4896a8b9ef99b1e3cedf630 2.012430217000 1197769 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": 749774, "vin": [ { "gen": { "height": 749764 } } ], "vout": [ { "amount": 2012430217, "target": { "key": "7287d44c5830be4ac32fd294d33aae29a4a6af65f4896a8b9ef99b1e3cedf630" } } ], "extra": [ 1, 52, 182, 239, 229, 173, 254, 136, 56, 112, 237, 28, 143, 116, 195, 25, 71, 35, 148, 34, 136, 77, 5, 125, 103, 118, 105, 90, 37, 232, 149, 85, 199, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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