Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cf825fd3ce66d16bf5b51e3697f1144322147013b4a2df38c634017d3c64585

Tx prefix hash: f9f36abfb23f7445f5a59f97bd4f6d3d35f1a591c0e9415a3ae6f872a6b15d24
Tx public key: 789ef1d4a7eca5cb9a88c9ab1113ddbc6dfd3eaf3172fadedbdd0c70a8f78b72
Timestamp: 1675055492 Timestamp [UCT]: 2023-01-30 05:11:32 Age [y:d:h:m:s]: 02:101:17:00:58
Block: 685838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 594321 RingCT/type: yes/0
Extra: 01789ef1d4a7eca5cb9a88c9ab1113ddbc6dfd3eaf3172fadedbdd0c70a8f78b72021100000012835e4d22000000000000000000

1 output(s) for total of 3.277433852000 dcy

stealth address amount amount idx
00: 3ae479cc89318071c5f2e6aeec606a716a486c7949a2dbc5a2682dd573f90eb9 3.277433852000 1128233 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": 685848, "vin": [ { "gen": { "height": 685838 } } ], "vout": [ { "amount": 3277433852, "target": { "key": "3ae479cc89318071c5f2e6aeec606a716a486c7949a2dbc5a2682dd573f90eb9" } } ], "extra": [ 1, 120, 158, 241, 212, 167, 236, 165, 203, 154, 136, 201, 171, 17, 19, 221, 188, 109, 253, 62, 175, 49, 114, 250, 222, 219, 221, 12, 112, 168, 247, 139, 114, 2, 17, 0, 0, 0, 18, 131, 94, 77, 34, 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