Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ebd3ac1d6b97d018f0fd13924ce1ec315e1fda888ff28f4ac7a73b08a0ccb4b7

Tx prefix hash: f98e0a76784d73afd0f4d666aa5b86a53119f1129f115a05cff81f657f9179d7
Tx public key: 3d8d8f7fccd63003a987ef5f775c94db39c2ed2177b8e814bfc2eff4a4639327
Timestamp: 1716348910 Timestamp [UCT]: 2024-05-22 03:35:10 Age [y:d:h:m:s]: 00:232:10:09:28
Block: 1027292 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 166343 RingCT/type: yes/0
Extra: 013d8d8f7fccd63003a987ef5f775c94db39c2ed2177b8e814bfc2eff4a463932702110000000259dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 46bd4c2293b21717b462e415fb2375399329c283ffa78883979736903d2f014d 0.600000000000 1494831 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": 1027302, "vin": [ { "gen": { "height": 1027292 } } ], "vout": [ { "amount": 600000000, "target": { "key": "46bd4c2293b21717b462e415fb2375399329c283ffa78883979736903d2f014d" } } ], "extra": [ 1, 61, 141, 143, 127, 204, 214, 48, 3, 169, 135, 239, 95, 119, 92, 148, 219, 57, 194, 237, 33, 119, 184, 232, 20, 191, 194, 239, 244, 164, 99, 147, 39, 2, 17, 0, 0, 0, 2, 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