Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 920802a231d3bf65bc0821a49df295d64c2784c9db4ad89476d5cc1c9640a208

Tx prefix hash: 4a2d3bd1692c877591abf513d2e7fb7dd1d2b03c9068c4ecbefeb70f6e9c2554
Tx public key: 6f5f0feb540adf79d7d48d57039158c17126f57e6494a9aa3372531992cd2245
Timestamp: 1712366592 Timestamp [UCT]: 2024-04-06 01:23:12 Age [y:d:h:m:s]: 00:280:18:34:06
Block: 994241 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200993 RingCT/type: yes/0
Extra: 016f5f0feb540adf79d7d48d57039158c17126f57e6494a9aa3372531992cd224502110000000659dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1fd63191fc35ce287e09c82b955ddaba65ae84d479f9ee83ab3cf65d3a83e19f 0.600000000000 1454643 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": 994251, "vin": [ { "gen": { "height": 994241 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1fd63191fc35ce287e09c82b955ddaba65ae84d479f9ee83ab3cf65d3a83e19f" } } ], "extra": [ 1, 111, 95, 15, 235, 84, 10, 223, 121, 215, 212, 141, 87, 3, 145, 88, 193, 113, 38, 245, 126, 100, 148, 169, 170, 51, 114, 83, 25, 146, 205, 34, 69, 2, 17, 0, 0, 0, 6, 89, 218, 211, 245, 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