Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f3e2b62aac099947a16c10c766ba7e1385dd43ca2b232655e913e75326b02ebb

Tx prefix hash: 626580b87e5fe203a02902d44fb044712fb10a1677f650b1a16a3142d468621c
Tx public key: 2433b977d3be8b4f1c109713be21f9b06fc40bf6b76656d69259eef1ef75bc29
Timestamp: 1672895249 Timestamp [UCT]: 2023-01-05 05:07:29 Age [y:d:h:m:s]: 02:015:12:42:21
Block: 667890 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 532983 RingCT/type: yes/0
Extra: 012433b977d3be8b4f1c109713be21f9b06fc40bf6b76656d69259eef1ef75bc2902110000000152542ceb000000000000000000

1 output(s) for total of 3.758401182000 dcy

stealth address amount amount idx
00: 44e3edc5bf0fc1da92e60d5d1042c60b45adb84192c4db2b27690cb3b146a0f3 3.758401182000 1109109 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": 667900, "vin": [ { "gen": { "height": 667890 } } ], "vout": [ { "amount": 3758401182, "target": { "key": "44e3edc5bf0fc1da92e60d5d1042c60b45adb84192c4db2b27690cb3b146a0f3" } } ], "extra": [ 1, 36, 51, 185, 119, 211, 190, 139, 79, 28, 16, 151, 19, 190, 33, 249, 176, 111, 196, 11, 246, 183, 102, 86, 214, 146, 89, 238, 241, 239, 117, 188, 41, 2, 17, 0, 0, 0, 1, 82, 84, 44, 235, 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